On Tue, 2010-03-16 at 17:40 +0000, David Howells wrote: > Trond Myklebust <Trond.Myklebust@xxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
