From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Andre Heider <a.heider@gmail.com>,
Rick Macklem <rmacklem@uoguelph.ca>,
linux-nfs@vger.kernel.org
Subject: Re: Error writing to nfs4 with 3.11-rc1
Date: Fri, 19 Jul 2013 12:13:13 -0400 [thread overview]
Message-ID: <20130719161313.GA20026@fieldses.org> (raw)
In-Reply-To: <F3EFA483-0662-4226-AAF3-DCF12D48485E@oracle.com>
On Wed, Jul 17, 2013 at 04:54:59PM -0400, Chuck Lever wrote:
> By the way, the NFSv4 OPEN request parsing in Wireshark 1.10.0 is totally screwed up. Has anyone reported this to the Wireshark community? Wireshark 1.8.8 appears to parse OPEN requests correctly, and is able to handle the 3-word bitmask correctly.
What exactly is screwed up?
For what it's worth, I took a quick look at the 3.11 trace with the
latest head from http://code.wireshark.org/git/wireshark and nothing
jumped out at me.
--b.
next prev parent reply other threads:[~2013-07-19 16:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 18:55 Error writing to nfs4 with 3.11-rc1 Andre Heider
2013-07-17 19:10 ` Chuck Lever
2013-07-17 19:35 ` Andre Heider
2013-07-17 20:54 ` Chuck Lever
2013-07-19 16:13 ` J. Bruce Fields [this message]
2013-07-19 16:33 ` Chuck Lever
2013-07-19 17:55 ` J. Bruce Fields
2013-07-19 18:03 ` Chuck Lever
2013-07-24 14:26 ` J. Bruce Fields
2013-07-17 21:59 ` Myklebust, Trond
2013-07-18 14:57 ` Andre Heider
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=20130719161313.GA20026@fieldses.org \
--to=bfields@fieldses.org \
--cc=a.heider@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rmacklem@uoguelph.ca \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.