path: root/fs/nfs/pnfs.c
diff options
authorTrond Myklebust <trond.myklebust@hammerspace.com>2018-06-23 13:35:28 -0400
committerTrond Myklebust <trond.myklebust@hammerspace.com>2018-07-26 16:25:24 -0400
commit00bcbe119f915dec256f211f9dbfc93cb64773bc (patch)
treefe62cb22048f7c616504b10b32c7c964f4f2f15e /fs/nfs/pnfs.c
parentpNFS: Don't discard layout segments that are marked for return (diff)
pNFS: Don't update the stateid when replying NFS4ERR_DELAY to a layout recall
RFC5661 doesn't state directly that the client should update the layout stateid if it returns NFS4ERR_NOMATCHING_LAYOUT in response to a recall, however it does state that this error will "cleanly indicate completion" on par with returning the layout. For this reason, we assume that the client should update the layout stateid. The Linux pNFS server definitely does expect this behaviour. However, if the client replies NFS4ERR_DELAY, then it is stating that the recall was not processed, so it would be very wrong to update the layout stateid. Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Diffstat (limited to 'fs/nfs/pnfs.c')
0 files changed, 0 insertions, 0 deletions