From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-nfs@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3.18.1: broken directory with one file too many
Date: Thu, 18 Dec 2014 15:42:53 +0000 (UTC) [thread overview]
Message-ID: <pan.2014.12.18.15.42.53@googlemail.com> (raw)
In-Reply-To: 20141218151914.GB18179@fieldses.org
On Thu, 18 Dec 2014 10:19:14 -0500, J. Bruce Fields wrote:
> On Thu, Dec 18, 2014 at 09:58:06AM -0500, Benjamin Coddington wrote:
>> Frame 36 of nfs-client.pcap has this interesting string:
>>
>> 0ff0 00 01 3b f6 fb b6 26 16 8f 7c 00 00 00 41 62 74
>> ..;...&..|...Abt 1000 72 66 73 2d 32 30 00 00 00 00 00 00 00 00 30 36
>> rfs-20........06 1010 2d 66 69 78 2d 64 65 61 64 6c 6f 63 6b 2d 77 68
>> -fix-deadlock-wh 1020 65 6e 2d 6d 6f 75 6e 74 69 6e 67 2d 61 2d 64
>> 65 en-mounting-a-de 1030 67 72 61 64 65 64 2d 66 73 2e 70 61 74 63
>> 68 00 graded-fs.patch.
>
> Yes, that looks like the server messing up the encoding of the reply.
>
> Holger, what's the difference between nfs-client.pcap and
> nfs-server.pcap?
One is the client, one is the server :-)
No, really. Both 3.18.1, 64it, same userland/compiler/etc. and even same
CFLAGS for both kernel and userland. I built tcpdump on both (from
packages) and ran them back to back literally 10 seconds apart.
What "encoding" are we talking about here? The NFS RPC encoding?
(everything I know & remember about NFS is 15+ years old..)
thanks,
Holger
next prev parent reply other threads:[~2014-12-18 15:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 22:19 3.18.1: broken directory with one file too many Holger Hoffstätte
2014-12-17 21:22 ` J. Bruce Fields
2014-12-18 12:22 ` Holger Hoffstätte
2014-12-18 12:51 ` Holger Hoffstätte
2014-12-18 12:59 ` Holger Hoffstätte
2014-12-18 14:48 ` J. Bruce Fields
2014-12-18 14:58 ` Benjamin Coddington
2014-12-18 15:19 ` J. Bruce Fields
2014-12-18 15:42 ` Holger Hoffstätte [this message]
2014-12-18 16:32 ` J. Bruce Fields
2014-12-18 16:42 ` Holger Hoffstätte
2014-12-18 17:06 ` J. Bruce Fields
2014-12-18 19:44 ` Holger Hoffstätte
2014-12-20 18:02 ` J. Bruce Fields
2014-12-20 18:50 ` Holger Hoffstätte
2015-01-07 0:25 ` Holger Hoffstätte
2015-01-07 18:21 ` J. Bruce Fields
2015-01-07 20:06 ` [PATCH] nfsd4: tweak rd_dircount accounting J. Bruce Fields
2014-12-18 17:18 ` 3.18.1: broken directory with one file too many J. Bruce Fields
2014-12-18 15:35 ` Holger Hoffstätte
2014-12-18 16:30 ` J. Bruce Fields
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=pan.2014.12.18.15.42.53@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
/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