tree 55f461a7a79a1822aa15c955941ec35aee04feb0
parent 0afb3bc53435b31fe66bb9305cdd8a3a80f181ca
author Trond Myklebust <trond.myklebust@hammerspace.com> 1635299800 -0400
committer Greg Kroah-Hartman <gregkh@linuxfoundation.org> 1637240665 +0100

NFSv4: Fix a regression in nfs_set_open_stateid_locked()

[ Upstream commit 01d29f87fcfef38d51ce2b473981a5c1e861ac0a ]

If we already hold open state on the client, yet the server gives us a
completely different stateid to the one we already hold, then we
currently treat it as if it were an out-of-sequence update, and wait for
5 seconds for other updates to come in.
This commit fixes the behaviour so that we immediately start processing
of the new stateid, and then leave it to the call to
nfs4_test_and_free_stateid() to decide what to do with the old stateid.

Fixes: b4868b44c562 ("NFSv4: Wait for stateid updates after CLOSE/OPEN_DOWNGRADE")
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>