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>
This commit is contained in:
Родитель
aa3d1faebe
Коммит
6ce7dc9407
|
@ -224,7 +224,8 @@ static int nfs4_stat_to_errno(int);
|
||||||
encode_getattr_maxsz)
|
encode_getattr_maxsz)
|
||||||
#define NFS4_dec_setattr_sz (compound_decode_hdr_maxsz + \
|
#define NFS4_dec_setattr_sz (compound_decode_hdr_maxsz + \
|
||||||
decode_putfh_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 + \
|
#define NFS4_enc_fsinfo_sz (compound_encode_hdr_maxsz + \
|
||||||
encode_putfh_maxsz + \
|
encode_putfh_maxsz + \
|
||||||
encode_fsinfo_maxsz)
|
encode_fsinfo_maxsz)
|
||||||
|
|
Загрузка…
Ссылка в новой задаче