diff options
| author | J. Bruce Fields <bfields@redhat.com> | 2013-06-21 11:48:11 -0400 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-07-13 11:03:41 -0700 |
| commit | ffdae5d98228dfbf7479cb777853ca031fbdfd3d (patch) | |
| tree | 299ebdc4b6bdf138033862be67ad5c2c1a27bd46 | |
| parent | 6d2698aa29a15559b89c54b86523632ea4110b6c (diff) | |
| download | linux-3.10-ffdae5d98228dfbf7479cb777853ca031fbdfd3d.tar.gz linux-3.10-ffdae5d98228dfbf7479cb777853ca031fbdfd3d.tar.bz2 linux-3.10-ffdae5d98228dfbf7479cb777853ca031fbdfd3d.zip | |
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>
| -rw-r--r-- | fs/nfsd/nfs4xdr.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/nfsd/nfs4xdr.c b/fs/nfsd/nfs4xdr.c index 17988461303..cb997b1bb39 100644 --- a/fs/nfsd/nfs4xdr.c +++ b/fs/nfsd/nfs4xdr.c @@ -161,8 +161,8 @@ static __be32 *read_buf(struct nfsd4_compoundargs *argp, u32 nbytes) */ memcpy(p, argp->p, avail); /* step to next page */ - argp->p = page_address(argp->pagelist[0]); argp->pagelist++; + argp->p = page_address(argp->pagelist[0]); if (argp->pagelen < PAGE_SIZE) { argp->end = argp->p + (argp->pagelen>>2); argp->pagelen = 0; |