From: Chuck Lever Date: Tue, 8 May 2007 22:23:28 +0000 (-0400) Subject: NFS: NFS client underestimates how large an NFSv4 SETATTR reply can be X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=6ce7dc940701cf3fde3c6e826a696b333092cbb1;p=GitHub%2FLineageOS%2Fandroid_kernel_samsung_universal7580.git 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 Signed-off-by: Trond Myklebust --- diff --git a/fs/nfs/nfs4xdr.c b/fs/nfs/nfs4xdr.c index b8c28f2380a..f1e2b8cdf33 100644 --- a/fs/nfs/nfs4xdr.c +++ b/fs/nfs/nfs4xdr.c @@ -224,7 +224,8 @@ static int nfs4_stat_to_errno(int); encode_getattr_maxsz) #define NFS4_dec_setattr_sz (compound_decode_hdr_maxsz + \ decode_putfh_maxsz + \ - op_decode_hdr_maxsz + 3) + op_decode_hdr_maxsz + 3 + \ + nfs4_fattr_maxsz) #define NFS4_enc_fsinfo_sz (compound_encode_hdr_maxsz + \ encode_putfh_maxsz + \ encode_fsinfo_maxsz)