nfsd4: fix decoding of compounds across page boundaries
authorJ. Bruce Fields <bfields@redhat.com>
Fri, 21 Jun 2013 15:48:11 +0000 (11:48 -0400)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 13 Jul 2013 18:03:41 +0000 (11:03 -0700)
commitffdae5d98228dfbf7479cb777853ca031fbdfd3d
tree299ebdc4b6bdf138033862be67ad5c2c1a27bd46
parent6d2698aa29a15559b89c54b86523632ea4110b6c
nfsd4: fix decoding of compounds across page boundaries

commit 247500820ebd02ad87525db5d9b199e5b66f6636 upstream.

A freebsd NFSv4.0 client was getting rare IO errors expanding a tarball.
A network trace showed the server returning BAD_XDR on the final getattr
of a getattr+write+getattr compound.  The final getattr started on a
page boundary.

I believe the Linux client ignores errors on the post-write getattr, and
that that's why we haven't seen this before.

Reported-by: Rick Macklem <rmacklem@uoguelph.ca>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/nfsd/nfs4xdr.c