Skip to content

NFSv4.1 Fix gdia_maxcount calculation to fit in ca_maxresponsesize

[email protected] linux-nfs 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3NFSv4.1 Fix gdia_maxcount calculation to fit in ca_maxresponsesizefs/nfs/internal.h fs/nfs/nfs4filelayoutdev.c fs/nfs/nfs4xdr.c +1 more+11 -20 replies
2/3NFSv4.1 use pnfs_device maxcount for the blocklayout gdia_maxcountfs/nfs/blocklayout/blocklayout.c+1 -00 replies
3/3NFSv4.1 use pnfs_device maxcount for the objectlayout gdia_maxcountfs/nfs/objlayout/objlayout.c+1 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH Version 2 0/3] NFSv4.1 Fix gdia_maxcount calculation to fit in ca_maxresponsesize

From: Andy Adamson <[email protected]>

Quoted 5 lines

From Trond:
The problem is that pdev->pglen is used both as the total buffer length, as a function argument and as the reply message length (through the call to xdr_init_decode_pages). We really should split out those 3 different roles...

AFAICS there are two roles: the reply or total message length used for xdr_init_decode_pages (where it is also a function argument) and the gdia_maxcount.

Put the block and object layout change in separate patches for ease of backporting.

-->Andy

Andy Adamson (3):
NFSv4.1 Fix gdia_maxcount calculation to fit in ca_maxresponsesize NFSv4.1 use pnfs_device maxcount for the blocklayout gdia_maxcount NFSv4.1 use pnfs_device maxcount for the objectlayout gdia_maxcount

 fs/nfs/blocklayout/blocklayout.c | 1 +
 fs/nfs/internal.h                | 1 +
 fs/nfs/nfs4filelayoutdev.c       | 1 +
 fs/nfs/nfs4xdr.c                 | 8 +++++++-
 fs/nfs/objlayout/objlayout.c     | 1 +
 fs/nfs/pnfs.h                    | 3 ++-
 6 files changed, 13 insertions(+), 2 deletions(-)
Signature · 1 line
1.7.11.7