diff options
author | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2012-01-12 17:21:20 -0800 |
---|---|---|
committer | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2012-02-21 09:03:46 -0800 |
commit | 5e1ee6e1016763812018bf5c5e966992821dc47e (patch) | |
tree | f2acb5d76a39da392d1f43e5c78a5ffc1482ef71 /kernel/rcutree.c | |
parent | 50406b98b6372e7de21d903d2cf3914e9d64e094 (diff) | |
download | op-kernel-dev-5e1ee6e1016763812018bf5c5e966992821dc47e.zip op-kernel-dev-5e1ee6e1016763812018bf5c5e966992821dc47e.tar.gz |
rcu: Note that rcu_access_pointer() can be used for teardown
There is no convenient expression for rcu_deference_protected()
when it is used in tearing down multilinked structures following
a grace period. For example, suppose that an element containing an
RCU-protected pointer to a second element is removed from an enclosing
RCU-protected data structure, then the write-side lock is released,
and finally synchronize_rcu() is invoked to wait for a grace period.
Then it is necessary to traverse the pointer in order to free up the
second element. But we are not in an RCU read-side critical section
and we are holding no locks, so the usual rcu_dereference_check() and
rcu_dereference_protected() primitives are not appropriate. Neither
is rcu_dereference_raw(), as it is intended for use in data structures
where the user defines the locking design (for example, list_head).
So this responsibility is added to rcu_access_pointer()'s list, and
this commit updates rcu_assign_pointer()'s header comment accordingly.
Suggested-by: David Howells <dhowells@redhat.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Acked-by: David Howells <dhowells@redhat.com>
Diffstat (limited to 'kernel/rcutree.c')
0 files changed, 0 insertions, 0 deletions