git://ftp.safe.ca / safe / jmp / linux-2.6 / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: aa3d1fa) | patch
NFS: NFS client underestimates how large an NFSv4 SETATTR reply can be
authorChuck Lever <chuck.lever@oracle.com>
Tue, 8 May 2007 22:23:28 +0000 (18:23 -0400)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Wed, 9 May 2007 21:58:00 +0000 (17:58 -0400)
commit6ce7dc940701cf3fde3c6e826a696b333092cbb1
tree0894788349bae7b0d1707dcab98505b5ada8a3eftree | snapshot
parentaa3d1faebe6e214cd96be0e587571477ff6fd9fccommit | diff
NFS: NFS client underestimates how large an NFSv4 SETATTR reply can be

The maximum size of an NFSv4 SETATTR compound reply should include the
GETATTR operation that we send.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
fs/nfs/nfs4xdr.c diff | blob | history
Full containers within linux kernel