projects / linux-2.6-block.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 7ce0171) | patch
NFSv4.1: Handle NFS4ERR_BADSLOT errors correctly
authorTrond Myklebust <Trond.Myklebust@netapp.com>
Tue, 11 Dec 2012 15:31:12 +0000 (10:31 -0500)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Tue, 11 Dec 2012 15:31:12 +0000 (10:31 -0500)
commit85563073741bd7935a6900d567ddaf907192270d
tree5d219f4fa3e9c60e5f20999cb7b5bc75632d1e92tree | snapshot
parent7ce0171d4f78992184faed87ea897d730b972965commit | diff
NFSv4.1: Handle NFS4ERR_BADSLOT errors correctly

Most (all) NFS4ERR_BADSLOT errors are due to the client failing to
respect the server's sr_highest_slotid limit. This mainly happens
due to reordered RPC requests.
The way to handle it is simply to drop the slot that we're using,
and retry using the new highest_slotid limits.

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
fs/nfs/nfs4proc.c diff | blob | blame | history
Linux 6.x block layer and io_uring tree(s)