From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Ext2 devel <ext2-devel@lists.sourceforge.net>,
NFS maillist <nfs@lists.sourceforge.net>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: htree+NFS (NFS client bug?)
Date: 27 Nov 2002 21:42:14 +0100 [thread overview]
Message-ID: <shsfztmeod5.fsf@charged.uio.no> (raw)
In-Reply-To: <20021127133318.GA8117@think.thunk.org>
>>>>> " " == Theodore Ts'o <tytso@mit.edu> writes:
> Well, even if the NFS server is generating bad cookies (and
> that may be possible), the NFS client should be more robust and
> not spin in a loop forever.
No. In this case, the problem appears to be that the cookie issued by
the server for the end of directory case is not unique.
If userland calls an extra 'readdir()' after EOF is reached, then as
far as the client is concerned, this sort of thing cannot be
distinguished from readdir()+seekdir()+readdir()..
Cheers,
Trond
next prev parent reply other threads:[~2002-11-27 20:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 23:44 Jeremy Fitzhardinge
2002-11-27 3:26 ` [NFS] " Trond Myklebust
2002-11-27 2:59 ` [Ext2-devel] " chrisl
2002-11-27 8:58 ` Jeremy Fitzhardinge
2002-11-27 15:00 ` [Ext2-devel] " Stephen C. Tweedie
2002-11-27 20:25 ` Trond Myklebust
2002-11-27 20:55 ` Stephen C. Tweedie
2002-11-27 22:44 ` Trond Myklebust
2002-11-28 16:41 ` Stephen C. Tweedie
2002-11-28 16:58 ` Trond Myklebust
2002-11-28 17:09 ` Stephen C. Tweedie
2002-11-28 17:57 ` Trond Myklebust
2002-11-28 16:44 ` Stephen C. Tweedie
2002-11-28 17:13 ` Stephen C. Tweedie
2002-11-28 17:44 ` Trond Myklebust
2002-11-28 20:00 ` Jeremy Fitzhardinge
2002-11-28 2:07 ` Jeremy Fitzhardinge
2002-11-28 2:46 ` Trond Myklebust
2002-11-27 13:33 ` Theodore Ts'o
2002-11-27 20:42 ` Trond Myklebust [this message]
2002-11-27 17:26 Jeremy Fitzhardinge
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=shsfztmeod5.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=tytso@mit.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
Powered by JetHome