summaryrefslogtreecommitdiff
path: root/fs/nfs/nfs4session.c
diff options
context:
space:
mode:
authorTrond Myklebust <Trond.Myklebust@netapp.com>2012-12-11 19:31:12 +0400
committerTrond Myklebust <Trond.Myklebust@netapp.com>2012-12-11 19:31:12 +0400
commit85563073741bd7935a6900d567ddaf907192270d (patch)
tree5d219f4fa3e9c60e5f20999cb7b5bc75632d1e92 /fs/nfs/nfs4session.c
parent7ce0171d4f78992184faed87ea897d730b972965 (diff)
downloadlinux-85563073741bd7935a6900d567ddaf907192270d.tar.xz
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>
Diffstat (limited to 'fs/nfs/nfs4session.c')
0 files changed, 0 insertions, 0 deletions