RFC nfsd: clean up CB_LAYOUTRECALL handling
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | nfsd: don't hold ls_mutex across a layout recallfs/ | +1 | 1 reply | |
| 2/2 | nfsd: give up on CB_LAYOUTRECALLs after two lease periodsfs/ | +25 | 5 replies |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Kinglong Mee | Christoph Hellwig |
|---|---|---|
| 1/2 | Reported-and-Tested-by | R-b |
| 2/2 | T-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [RFC PATCH 0/2] nfsd: clean up CB_LAYOUTRECALL handling
This is a proposal that should follow the broad outlines of what HCH was suggesting for CB_LAYOUTRECALL. It changes the code to treat 0 and NFS4ERR_DELAY returns equivalently, and also implements a scheme to give up on the client after two lease periods.
Note that this is _not_ tested, since I don't have a pnfs test rig on which to test this.
Jeff Layton (2):
nfsd: don't hold ls_mutex across a layout recall
nfsd: give up on CB_LAYOUTRECALLs after two lease periods
fs/nfsd/nfs4layouts.c | 37 ++++++++++++++++++++++++++----------- 1 file changed, 26 insertions(+), 11 deletions(-)
Signature · 1 line
2.5.0