["J. Bruce Fields" <bfields@xxxxxxxxxxxx>]

Wireshark suddenly seems to be failing to parse NFSv4 setattr operations
that it had no trouble with before.  OK, that or my NFSv4 client has
just gone haywire--I don't think, so, though; it looks like the
setattr's in the file (frames 26 and 32) are fine, and it's just
wireshark that's confused--maybe it thinks the preceding stateid is a
few bytes longer than it really is.

--b.