public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: David Howells <dhowells@redhat.com>
Cc: paulmck@linux.vnet.ibm.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 14:41:44 -0400	[thread overview]
Message-ID: <1268764904.3098.21.camel@localhost.localdomain> (raw)
In-Reply-To: <19197.1268761204@redhat.com>

On Tue, 2010-03-16 at 17:40 +0000, David Howells wrote: 
> Trond Myklebust <Trond.Myklebust@netapp.com> wrote:
> 
> > > 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.
> 
> In that case, surely you can't detach the credentials pointer until the
> callback is invoked?

We can, because the process that is traversing the list has to lock the
delegation and test whether it is still attached or not before it can
dereference and use the contents.

In fact, that credential pointer is only really meant to be used when we
need to return the delegation. Once we get to the nfs_free_delegation()
bit, it is no longer needed.

Cheers
  Trond

  reply	other threads:[~2010-03-16 18:42 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
2010-03-16 17:40     ` David Howells
2010-03-16 18:41       ` Trond Myklebust [this message]
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=1268764904.3098.21.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