Lines Matching refs:rcu_dereference

1 PROPER CARE AND FEEDING OF RETURN VALUES FROM rcu_dereference()
3 Most of the time, you can use values from rcu_dereference() or one of
11 o	You must use one of the rcu_dereference() family of primitives
15 	Without one of the rcu_dereference() primitives, compilers
17 	different values for a single pointer!  Without rcu_dereference(),
22 	In addition, the volatile cast in rcu_dereference() prevents the
28 o	You are only permitted to use rcu_dereference on pointer values.
49 	subsequent accesses no longer depend on the rcu_dereference(),
52 	Of course, if "p" is a pointer from rcu_dereference(), and "a"
55 	the rcu_dereference(), thus maintaining proper ordering.
59 	(directly or indirectly) from rcu_dereference(), you may need to
73 		p = rcu_dereference(gp)
85 	rcu_dereference() against non-NULL values.  As Linus Torvalds
88 	obtained from rcu_dereference().  For example:
90 		p = rcu_dereference(gp);
98 		p = rcu_dereference(gp);
104 	rcu_dereference().  This could result in bugs due to misordering.
112 		it is safe to compare pointers from rcu_dereference()
125 		of rcu_dereference().
152 		rcu_dereference().  In this case, both pointers depend
153 		on one rcu_dereference() or another, so you get proper
170 		pointer.  Note that the volatile cast in rcu_dereference()
227 		p = rcu_dereference(gp2);
231 		q = rcu_dereference(gp1);  /* Guaranteed non-NULL. */
284 		p = rcu_dereference(gp2);
289 		q = rcu_dereference(gp1);  /* Guaranteed non-NULL. */
303 If a pointer obtained from rcu_dereference() compares not-equal to some
307 guarantees that RCU depends on.  And the volatile cast in rcu_dereference()
310 But without rcu_dereference(), the compiler knows more than you might
352 In short, rcu_dereference() is -not- optional when you are going to