From: Jeff Layton <jlayton@primarydata.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org, hch@infradead.org
Subject: [PATCH v2 37/38] nfsd: don't thrash the cl_lock while freeing an open stateid
Date: Tue, 29 Jul 2014 16:34:20 -0400 [thread overview]
Message-ID: <1406666061-14175-38-git-send-email-jlayton@primarydata.com> (raw)
In-Reply-To: <1406666061-14175-1-git-send-email-jlayton@primarydata.com>
When we remove the client_mutex, we'll have a potential race between
FREE_STATEID and CLOSE.
The root of the problem is that we are walking the st_locks list,
dropping the spinlock and then trying to release the persistent
reference to the lockstateid. In between, a FREE_STATEID call can come
along and take the lock, find the stateid and then try to put the
reference. That leads to a double put.
Fix this by not releasing the cl_lock in order to release each lock
stateid. Use put_generic_stateid_locked to unhash them and gather them
onto a list, and free_ol_stateid_reaplist to free any that end up on the
list.
Signed-off-by: Jeff Layton <jlayton@primarydata.com>
---
fs/nfsd/nfs4state.c | 34 +++++++++++++++++++---------------
1 file changed, 19 insertions(+), 15 deletions(-)
diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
index 879342bc16b2..1f67a96c4941 100644
--- a/fs/nfsd/nfs4state.c
+++ b/fs/nfsd/nfs4state.c
@@ -1077,27 +1077,26 @@ static void release_lockowner(struct nfs4_lockowner *lo)
nfs4_put_stateowner(&lo->lo_owner);
}
-static void release_open_stateid_locks(struct nfs4_ol_stateid *open_stp)
- __releases(&open_stp->st_stateowner->so_client->cl_lock)
- __acquires(&open_stp->st_stateowner->so_client->cl_lock)
+static void release_open_stateid_locks(struct nfs4_ol_stateid *open_stp,
+ struct list_head *reaplist)
{
struct nfs4_ol_stateid *stp;
while (!list_empty(&open_stp->st_locks)) {
stp = list_entry(open_stp->st_locks.next,
struct nfs4_ol_stateid, st_locks);
- spin_unlock(&open_stp->st_stateowner->so_client->cl_lock);
- release_lock_stateid(stp);
- spin_lock(&open_stp->st_stateowner->so_client->cl_lock);
+ unhash_lock_stateid(stp);
+ put_ol_stateid_locked(stp, reaplist);
}
}
-static void unhash_open_stateid(struct nfs4_ol_stateid *stp)
+static void unhash_open_stateid(struct nfs4_ol_stateid *stp,
+ struct list_head *reaplist)
{
lockdep_assert_held(&stp->st_stid.sc_client->cl_lock);
unhash_generic_stateid(stp);
- release_open_stateid_locks(stp);
+ release_open_stateid_locks(stp, reaplist);
}
static void release_open_stateid(struct nfs4_ol_stateid *stp)
@@ -1105,7 +1104,7 @@ static void release_open_stateid(struct nfs4_ol_stateid *stp)
LIST_HEAD(reaplist);
spin_lock(&stp->st_stid.sc_client->cl_lock);
- unhash_open_stateid(stp);
+ unhash_open_stateid(stp, &reaplist);
put_ol_stateid_locked(stp, &reaplist);
spin_unlock(&stp->st_stid.sc_client->cl_lock);
free_ol_stateid_reaplist(&reaplist);
@@ -1145,7 +1144,7 @@ static void release_openowner(struct nfs4_openowner *oo)
while (!list_empty(&oo->oo_owner.so_stateids)) {
stp = list_first_entry(&oo->oo_owner.so_stateids,
struct nfs4_ol_stateid, st_perstateowner);
- unhash_open_stateid(stp);
+ unhash_open_stateid(stp, &reaplist);
put_ol_stateid_locked(stp, &reaplist);
}
spin_unlock(&clp->cl_lock);
@@ -4701,16 +4700,21 @@ out:
static void nfsd4_close_open_stateid(struct nfs4_ol_stateid *s)
{
struct nfs4_client *clp = s->st_stid.sc_client;
+ LIST_HEAD(reaplist);
s->st_stid.sc_type = NFS4_CLOSED_STID;
spin_lock(&clp->cl_lock);
- unhash_open_stateid(s);
- spin_unlock(&clp->cl_lock);
+ unhash_open_stateid(s, &reaplist);
- if (clp->cl_minorversion)
- nfs4_put_stid(&s->st_stid);
- else
+ if (clp->cl_minorversion) {
+ put_ol_stateid_locked(s, &reaplist);
+ spin_unlock(&clp->cl_lock);
+ free_ol_stateid_reaplist(&reaplist);
+ } else {
+ spin_unlock(&clp->cl_lock);
+ free_ol_stateid_reaplist(&reaplist);
move_to_close_lru(s, clp->net);
+ }
}
/*
--
1.9.3
next prev parent reply other threads:[~2014-07-29 20:35 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 20:33 [PATCH v2 00/38] nfsd: stateid and stateowner refcounting overhaul Jeff Layton
2014-07-29 20:33 ` [PATCH v2 01/38] nfsd: Add reference counting to the lock and open stateids Jeff Layton
2014-07-29 20:33 ` [PATCH v2 02/38] nfsd: Cleanup the freeing of stateids Jeff Layton
2014-07-29 20:33 ` [PATCH v2 03/38] nfsd: Add a struct nfs4_file field to struct nfs4_stid Jeff Layton
2014-07-30 0:54 ` J. Bruce Fields
2014-07-30 1:28 ` Jeff Layton
2014-07-29 20:33 ` [PATCH v2 04/38] nfsd: Replace nfs4_ol_stateid->st_file with the st_stid.sc_file Jeff Layton
2014-07-29 20:33 ` [PATCH v2 05/38] nfsd4: use cl_lock to synchronize all stateid idr calls Jeff Layton
2014-07-29 20:33 ` [PATCH v2 06/38] nfsd: do filp_close in sc_free callback for lock stateids Jeff Layton
2014-07-29 20:33 ` [PATCH v2 07/38] nfsd: Add locking to protect the state owner lists Jeff Layton
2014-07-29 20:33 ` [PATCH v2 08/38] nfsd: clean up races in lock stateid searching and creation Jeff Layton
2014-07-29 20:33 ` [PATCH v2 09/38] nfsd: ensure atomicity in nfsd4_free_stateid and nfsd4_validate_stateid Jeff Layton
2014-07-29 20:33 ` [PATCH v2 10/38] nfsd: Add reference counting to lock stateids Jeff Layton
2014-07-29 20:33 ` [PATCH v2 11/38] nfsd: nfsd4_locku() must reference the lock stateid Jeff Layton
2014-07-29 20:33 ` [PATCH v2 12/38] nfsd: Ensure that nfs4_open_delegation() references the delegation stateid Jeff Layton
2014-07-29 20:33 ` [PATCH v2 13/38] nfsd: nfsd4_process_open2() must reference " Jeff Layton
2014-07-29 20:33 ` [PATCH v2 14/38] nfsd: nfsd4_process_open2() must reference the open stateid Jeff Layton
2014-07-29 20:33 ` [PATCH v2 15/38] nfsd: Prepare nfsd4_close() for open stateid referencing Jeff Layton
2014-07-29 20:33 ` [PATCH v2 16/38] nfsd: nfsd4_open_confirm() must reference the open stateid Jeff Layton
2014-07-29 20:34 ` [PATCH v2 17/38] nfsd: Add reference counting to nfs4_preprocess_confirmed_seqid_op Jeff Layton
2014-07-29 20:34 ` [PATCH v2 18/38] nfsd: Migrate the stateid reference into nfs4_preprocess_seqid_op Jeff Layton
2014-07-29 20:34 ` [PATCH v2 19/38] nfsd: Migrate the stateid reference into nfs4_lookup_stateid() Jeff Layton
2014-07-29 20:34 ` [PATCH v2 20/38] nfsd: Migrate the stateid reference into nfs4_find_stateid_by_type() Jeff Layton
2014-07-29 20:34 ` [PATCH v2 21/38] nfsd: Add reference counting to state owners Jeff Layton
2014-07-29 20:34 ` [PATCH v2 22/38] nfsd: Add a mutex to protect the NFSv4.0 open owner replay cache Jeff Layton
2014-07-29 20:34 ` [PATCH v2 23/38] nfsd: clean up lockowner refcounting when finding them Jeff Layton
2014-07-29 20:34 ` [PATCH v2 24/38] nfsd: add an operation for unhashing a stateowner Jeff Layton
2014-07-29 20:34 ` [PATCH v2 25/38] nfsd: Make lock stateid take a reference to the lockowner Jeff Layton
2014-07-29 20:34 ` [PATCH v2 26/38] nfsd: clean up refcounting for lockowners Jeff Layton
2014-07-29 20:34 ` [PATCH v2 27/38] nfsd: make openstateids hold references to their openowners Jeff Layton
2014-07-29 20:34 ` [PATCH v2 28/38] nfsd: don't allow CLOSE to proceed until refcount on stateid drops Jeff Layton
2014-07-29 20:34 ` [PATCH v2 29/38] nfsd: Protect adding/removing open state owners using client_lock Jeff Layton
2014-07-29 20:34 ` [PATCH v2 30/38] nfsd: Protect adding/removing lock " Jeff Layton
2014-07-29 20:34 ` [PATCH v2 31/38] nfsd: Move the open owner hash table into struct nfs4_client Jeff Layton
2014-07-29 20:34 ` [PATCH v2 32/38] nfsd: clean up and reorganize release_lockowner Jeff Layton
2014-07-29 20:34 ` [PATCH v2 33/38] nfsd: add locking to stateowner release Jeff Layton
2014-07-29 20:34 ` [PATCH v2 34/38] nfsd: optimize destroy_lockowner cl_lock thrashing Jeff Layton
2014-07-29 20:34 ` [PATCH v2 35/38] nfsd: close potential race in nfsd4_free_stateid Jeff Layton
2014-07-29 20:34 ` [PATCH v2 36/38] nfsd: reduce cl_lock thrashing in release_openowner Jeff Layton
2014-07-29 20:34 ` Jeff Layton [this message]
2014-07-29 20:34 ` [PATCH v2 38/38] nfsd: rename unhash_generic_stateid to unhash_ol_stateid Jeff Layton
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=1406666061-14175-38-git-send-email-jlayton@primarydata.com \
--to=jlayton@primarydata.com \
--cc=bfields@fieldses.org \
--cc=hch@infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.