Lines Matching refs:pointer

10 macro's load of the pointer to the later use of that pointer to compute
28 	to load an RCU-protected pointer, otherwise CONFIG_PROVE_RCU
33 	different values for a single pointer!  Without rcu_dereference(),
34 	DEC Alpha can load a pointer, dereference that pointer, and
36 	of the pointer.  (As noted later, in recent kernels READ_ONCE()
40 	compiler from deducing the resulting pointer value.  Please see
43 	value of the pointer, and thus cause misordering.
51 -	You are only permitted to use rcu_dereference() on pointer values.
55 	cast the pointer to uintptr_t in order to:
58 		bits of that pointer.  This clearly means that the pointer
65 	It is important to cast the value back to pointer before
75 	Of course, if "p" is a pointer from rcu_dereference(), and "a"
110 	substitute the pointer you are comparing against for the pointer
131 	-	The comparison was against the NULL pointer.  If the
132 		compiler knows that the pointer is NULL, you had better
138 	-	The pointer is never dereferenced after being compared.
145 		Note that if the pointer comparison is done outside
146 		of an RCU read-side critical section, and the pointer
156 	-	The comparison is against a pointer that references memory
180 	-	The pointer being compared against also came from
199 		pointer.  Note that the volatile cast in rcu_dereference()
203 		pointer takes on only one of two values, a not-equal
205 		compiler needs to deduce the value of the pointer.
344 If a pointer obtained from rcu_dereference() compares not-equal to some
345 other pointer, the compiler normally has no clue what the value of the
346 first pointer might be.  This lack of knowledge prevents the compiler
394 dereference the resulting pointer.
448 	of locks or reference counters suffices to protect the pointer,
492 "__rcu" marker.  If you mark a pointer declaration, whether in a structure
494 this pointer is accessed directly.  It will also cause sparse to complain
495 if a pointer not marked with "__rcu" is accessed using rcu_dereference()