From: Chuck Lever <chuck.lever@oracle.com>
To: linux-nfs@vger.kernel.org
Subject: [PATCH 21/21] NFS: Fix possible endless state recovery wait
Date: Thu, 17 Oct 2013 14:14:10 -0400 [thread overview]
Message-ID: <20131017181410.1073.25348.stgit@nfsvm18.us.oracle.com> (raw)
In-Reply-To: <20131017180630.1073.18400.stgit@nfsvm18.us.oracle.com>
In nfs4_wait_clnt_recover(), hold a reference to the clp being
waited on. The state manager can reduce clp->cl_count to 1, in
which case the nfs_put_client() in nfs4_run_state_manager() can
free *clp before wait_on_bit() returns and allows
nfs4_wait_clnt_recover() to run again.
The behavior at that point is non-deterministic. If the waited-on
bit still happens to be zero, wait_on_bit() will wake the waiter as
expected. If the bit is set again (say, if the memory was poisoned
when freed) wait_on_bit() can leave the waiter asleep.
This is a narrow fix which ensures the safety of accessing *clp in
nfs4_wait_clnt_recover(), but does not address the continued use
of a possibly freed *clp after nfs4_wait_clnt_recover() returns
(see nfs_end_delegation_return(), for example).
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
fs/nfs/nfs4state.c | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c
index 6daa064..1a3cb26 100644
--- a/fs/nfs/nfs4state.c
+++ b/fs/nfs/nfs4state.c
@@ -1255,14 +1255,16 @@ int nfs4_wait_clnt_recover(struct nfs_client *clp)
might_sleep();
+ atomic_inc(&clp->cl_count);
res = wait_on_bit(&clp->cl_state, NFS4CLNT_MANAGER_RUNNING,
nfs_wait_bit_killable, TASK_KILLABLE);
if (res)
- return res;
-
+ goto out;
if (clp->cl_cons_state < 0)
- return clp->cl_cons_state;
- return 0;
+ res = clp->cl_cons_state;
+out:
+ nfs_put_client(clp);
+ return res;
}
int nfs4_client_recover_expired_lease(struct nfs_client *clp)
prev parent reply other threads:[~2013-10-17 18:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 18:12 [PATCH 00/21] Basic NFSv4 migration support Chuck Lever
2013-10-17 18:12 ` [PATCH 01/21] SUNRPC: Modify synopsis of rpc_client_register() Chuck Lever
2013-10-17 18:12 ` [PATCH 02/21] SUNRPC: Add a helper to switch the transport of an rpc_clnt Chuck Lever
2013-10-17 18:12 ` [PATCH 03/21] NFS: Add nfs4_update_server Chuck Lever
2013-10-17 18:12 ` [PATCH 04/21] NFS: Add functions to swap transports during migration recovery Chuck Lever
2013-10-17 18:12 ` [PATCH 05/21] NFS: Introduce a vector of migration recovery ops Chuck Lever
2013-10-17 18:12 ` [PATCH 06/21] NFS: Export _nfs_display_fhandle() Chuck Lever
2013-10-17 18:12 ` [PATCH 07/21] NFS: Add method to retrieve fs_locations during migration recovery Chuck Lever
2013-10-17 18:12 ` [PATCH 08/21] NFS: Add a super_block backpointer to the nfs_server struct Chuck Lever
2013-10-17 18:13 ` [PATCH 09/21] NFS: Add basic migration support to state manager thread Chuck Lever
2013-10-17 18:13 ` [PATCH 10/21] NFS: Re-use exit code in nfs4_async_handle_error() Chuck Lever
2013-10-17 18:13 ` [PATCH 11/21] NFS: Rename "stateid_invalid" label Chuck Lever
2013-10-17 18:13 ` [PATCH 12/21] NFS: Add migration recovery callouts in nfs4proc.c Chuck Lever
2013-10-17 18:13 ` [PATCH 13/21] NFS: Handle NFS4ERR_MOVED during delegation recall Chuck Lever
2013-10-17 18:13 ` [PATCH 14/21] NFS: Add method to detect whether an FSID is still on the server Chuck Lever
2013-10-17 18:13 ` [PATCH 15/21] NFS: Support NFS4ERR_LEASE_MOVED recovery in state manager Chuck Lever
2013-10-17 18:13 ` [PATCH 16/21] NFS: Implement support for NFS4ERR_LEASE_MOVED Chuck Lever
2013-10-17 18:13 ` [PATCH 17/21] NFS: Migration support for RELEASE_LOCKOWNER Chuck Lever
2013-10-17 18:13 ` [PATCH 18/21] NFS: Handle NFS4ERR_LEASE_MOVED during async RENEW Chuck Lever
2013-10-17 18:13 ` [PATCH 19/21] NFS: Handle SEQ4_STATUS_LEASE_MOVED Chuck Lever
2013-10-17 18:14 ` [PATCH 20/21] NFS: Set EXCHGID4_FLAG_SUPP_MOVED_MIGR Chuck Lever
2013-10-17 18:14 ` Chuck Lever [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131017181410.1073.25348.stgit@nfsvm18.us.oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).