From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Ext2 devel <ext2-devel@lists.sourceforge.net>,
NFS maillist <nfs@lists.sourceforge.net>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [Ext2-devel] Re: [NFS] htree+NFS (NFS client bug?)
Date: Thu, 28 Nov 2002 03:46:00 +0100 [thread overview]
Message-ID: <15845.33640.256556.123111@charged.uio.no> (raw)
In-Reply-To: <1038449223.1464.17.camel@ixodes.goop.org>
>>>>> " " == Jeremy Fitzhardinge <jeremy@goop.org> writes:
> Hm, I just did a run with 8k NFS packets, and the results are
> slightly different. There's only a single READDIR reply,
> fragmented over 3 IP packets. vg_include.h~51-kill-inceip
> still has a cookie of 1611747420, and vg_libpthread.vs is still
> the last entry returned, but it has a cookie of 0. As far as I
> can see, all the other cookies are unique.
AFAICS, the ext2/ext3 code is simply failing to initialize that last
cookie, and so knfsd is giving it the value of the cookie that was
passed by the client.
Cheers,
Trond
next prev parent reply other threads:[~2002-11-28 2:38 UTC|newest]
Thread overview: 20+ 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 [this message]
2002-11-27 13:33 ` Theodore Ts'o
2002-11-27 20:42 ` Trond Myklebust
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=15845.33640.256556.123111@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=sct@redhat.com \
/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
all inboxes | Powered by JetHome®