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
33 	by rcu_dereference().  If the array index no longer depends
34 	on rcu_dereference(), then both the compiler and the CPU
36 	rcu_dereference(), which can cause the array access to return
45 	on the rcu_dereference(), again possibly resulting in bugs due
48 	Of course, if "p" is a pointer from rcu_dereference(), and "a"
51 	the rcu_dereference(), thus maintaining proper ordering.
58 	accesses to no longer depend on the rcu_dereference(), causing
70 	(directly or indirectly) from rcu_dereference(), you may need to
85 		r1 = rcu_dereference(i1)
103 		r1 = rcu_dereference(i1)
113 	rcu_dereference() against non-NULL values.  As Linus Torvalds
116 	obtained from rcu_dereference().  For example:
118 		p = rcu_dereference(gp);
126 		p = rcu_dereference(gp);
132 	rcu_dereference().  This could result in bugs due to misordering.
140 		it is safe to compare pointers from rcu_dereference()
175 		rcu_dereference().  In this case, both pointers depend
176 		on one rcu_dereference() or another, so you get proper
193 		pointer.  Note that the volatile cast in rcu_dereference()
245 		p = rcu_dereference(gp2);
249 		q = rcu_dereference(gp1);  /* Guaranteed non-NULL. */
302 		p = rcu_dereference(gp2);
307 		q = rcu_dereference(gp1);  /* Guaranteed non-NULL. */
321 If a pointer obtained from rcu_dereference() compares not-equal to some
325 guarantees that RCU depends on.  And the volatile cast in rcu_dereference()
328 But without rcu_dereference(), the compiler knows more than you might
370 In short, rcu_dereference() is -not- optional when you are going to