NFSv4.1: We must release the sequence id when we fail to get a session slot
authorTrond Myklebust <Trond.Myklebust@netapp.com>
Mon, 29 Oct 2012 22:37:40 +0000 (18:37 -0400)
committerBen Hutchings <ben@decadent.org.uk>
Fri, 16 Nov 2012 16:47:04 +0000 (16:47 +0000)
commitd6d5a8514ee883d824427e5a70103c180ffbb6e9
tree79ed707b2b20eb381aa59192dc33be35c2a16452
parent0182399b8032adcc5123ac9ab4634c1f060cb7fd
NFSv4.1: We must release the sequence id when we fail to get a session slot

commit 2240a9e2d013d8269ea425b73e1d7a54c7bc141f upstream.

If we do not release the sequence id in cases where we fail to get a
session slot, then we can deadlock if we hit a recovery scenario.

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
[bwh: Backported to 3.2:
 - Adjust context
 - nfs4_setup_sequence() has an additional 'cache_reply' parameter]
Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
fs/nfs/nfs4proc.c