| commit | c489ee290bdbbace6bb63ebe6ebd4dd605819495 | |
| author | Trond Myklebust <Trond.Myklebust@netapp.com> | |
| Wed, 30 Jan 2013 18:04:10 +0000 (30 13:04 -0500) | ||
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | |
| Wed, 30 Jan 2013 22:45:15 +0000 (30 17:45 -0500) | ||
| tree | f1d41c565e0860cbd474c1bf4cfde37420d76c66 | treesnapshot (tar.gz zip) |
| parent | edd2e36fe8bd3cec4fa67e746d4c4a9246d0830e | commitdiff |
NFSv4.1: Handle NFS4ERR_DELAY when resetting the NFSv4.1 session
NFS4ERR_DELAY is a legal reply when we call DESTROY_SESSION. It
usually means that the server is busy handling an unfinished RPC
request. Just sleep for a second and then retry.
We also need to be able to handle the NFS4ERR_BACK_CHAN_BUSY return
value. If the NFS server has outstanding callbacks, we just want to
similarly sleep & retry.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: stable@vger.kernel.org
NFS4ERR_DELAY is a legal reply when we call DESTROY_SESSION. It
usually means that the server is busy handling an unfinished RPC
request. Just sleep for a second and then retry.
We also need to be able to handle the NFS4ERR_BACK_CHAN_BUSY return
value. If the NFS server has outstanding callbacks, we just want to
similarly sleep & retry.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: stable@vger.kernel.org
| fs/nfs/nfs4state.c | diffblobblamehistory |