Return-Path: linux-nfs-owner@vger.kernel.org Received: from fieldses.org ([174.143.236.118]:42353 "EHLO fieldses.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751762Ab3GSQNP (ORCPT ); Fri, 19 Jul 2013 12:13:15 -0400 Date: Fri, 19 Jul 2013 12:13:13 -0400 To: Chuck Lever Cc: Andre Heider , Rick Macklem , linux-nfs@vger.kernel.org Subject: Re: Error writing to nfs4 with 3.11-rc1 Message-ID: <20130719161313.GA20026@fieldses.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: From: "J. Bruce Fields" Sender: linux-nfs-owner@vger.kernel.org List-ID: 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.