From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: paulmck@linux.vnet.ibm.com
Cc: David Howells <dhowells@redhat.com>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NFS: Fix RCU warnings in nfs_inode_return_delegation_noreclaim()
Date: Tue, 16 Mar 2010 13:35:54 -0400 [thread overview]
Message-ID: <1268760954.3098.17.camel@localhost.localdomain> (raw)
In-Reply-To: <20100316171738.GN6709@linux.vnet.ibm.com>
On Tue, 2010-03-16 at 10:17 -0700, Paul E. McKenney wrote:
> On Tue, Mar 16, 2010 at 11:51:30AM +0000, David Howells wrote:
> > diff --git a/fs/nfs/delegation.c b/fs/nfs/delegation.c
> > index 2563beb..a77c735 100644
> > --- a/fs/nfs/delegation.c
> > +++ b/fs/nfs/delegation.c
> > @@ -37,8 +37,10 @@ static void nfs_free_delegation(struct nfs_delegation *delegation)
> > {
> > struct rpc_cred *cred;
> >
> > + rcu_read_lock();
> > cred = rcu_dereference(delegation->cred);
> > rcu_assign_pointer(delegation->cred, NULL);
>
> The lock is probably held here, in which case something like the
> following would work well without needing the artificial rcu_read_lock()
> and rcu_read_unlock():
No. The lock is not held here. At this point, the delegation has been
detached from the inode that pointed to it, and so we can free up its
contents.
We still need the call_rcu() to free up the allocated memory in order to
ensure that some process doing lockless traversal of the
clp->cl_delegations list doesn't crash.
> cred = rcu_dereference_check(delegation->cred,
> lockdep_is_held(&delegation->lock));
>
> > + rcu_read_unlock();
> > call_rcu(&delegation->rcu, nfs_free_delegation_callback);
> > if (cred)
> > put_rpccred(cred);
> > @@ -212,10 +214,12 @@ int nfs_inode_set_delegation(struct inode *inode, struct rpc_cred *cred, struct
> > spin_lock_init(&delegation->lock);
> >
> > spin_lock(&clp->cl_lock);
> > + rcu_read_lock();
> > if (rcu_dereference(nfsi->delegation) != NULL) {
>
> Same here, though I am not sure whether clp->cl_lock or something in
> nfs_inode should be used.
Yes. As I indicated to David in another email, the clp->cl_lock protects
us here, so it looks as if your suggestion above would be perfect.
> > if (memcmp(&delegation->stateid, &nfsi->delegation->stateid,
> > sizeof(delegation->stateid)) == 0 &&
> > delegation->type == nfsi->delegation->type) {
> > + rcu_read_unlock();
> > goto out;
> > }
> > /*
> > @@ -228,6 +232,7 @@ int nfs_inode_set_delegation(struct inode *inode, struct rpc_cred *cred, struct
> > if (delegation->type <= nfsi->delegation->type) {
> > freeme = delegation;
> > delegation = NULL;
> > + rcu_read_lock();
> > goto out;
> > }
> > freeme = nfs_detach_delegation_locked(nfsi, NULL);
next prev parent reply other threads:[~2010-03-16 17:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 11:51 [PATCH] NFS: Fix RCU warnings in nfs_inode_return_delegation_noreclaim() David Howells
2010-03-16 13:07 ` Trond Myklebust
2010-03-16 16:37 ` David Howells
2010-03-16 17:17 ` Paul E. McKenney
2010-03-16 17:35 ` Trond Myklebust [this message]
2010-03-16 17:40 ` David Howells
2010-03-16 18:41 ` Trond Myklebust
2010-03-16 18:10 ` Paul E. McKenney
2010-03-16 18:43 ` Trond Myklebust
2010-03-16 19:15 ` Paul E. McKenney
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=1268760954.3098.17.camel@localhost.localdomain \
--to=trond.myklebust@netapp.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/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