From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] Pathological 9P question.
Date: Mon, 4 Aug 2003 18:58:22 -0400 [thread overview]
Message-ID: <200308042258.h74MwM703088@augusta.math.psu.edu> (raw)
Here's a question about a pathological case. Read(5) says that a read
in a directory must have an offset of either 0, or the offset of the
previous read plus the number of bytes returned. Walk(5) says that a
walk to . (ie, a walk where nwnames == 0) and newfid != oldfid is
equivalent to cloning oldfid, and that both fids will point to the same
file. What is the expected behavior, then, if a read is executed in a
directory, the fid is cloned but not clunked, and then a read is
executed on the new fid using the appropriate offset for the old fid?
Should the read succeed or fail?
- Dan C.
next reply other threads:[~2003-08-04 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 22:58 Dan Cross [this message]
2003-08-04 23:39 ` Charles Forsyth
2003-08-04 23:53 ` rob pike, esq.
2003-08-05 0:11 ` Dan Cross
2003-08-05 0:21 ` rob pike, esq.
2003-08-05 3:34 ` jmk
2003-08-05 4:01 ` Dan Cross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200308042258.h74MwM703088@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).