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 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
