Lines Matching refs:must
28 RCU does allow -readers- to run (almost) naked, but -writers- must
53 pointer must be covered by rcu_read_lock(), rcu_read_lock_bh(),
94 One must usually liberally sprinkle memory barriers
105 reordered to precede earlier stores. RCU code must take all of
108 a. Readers must maintain proper ordering of their memory
144 and list_add_rcu() primitives must be used in order
151 primitive must be used to keep list_del()'s pointer
163 e. Updates must ensure that initialization of a given
171 must be written to be called from softirq context. In particular,
202 corresponding readers must use rcu_read_lock() and
204 synchronize_rcu_bh(), then the corresponding readers must
207 the corresponding readers must disable preemption, possibly
210 the corresponding readers must use srcu_read_lock() and
220 such cases is a must, of course! And the jury is still out on
293 list_for_each_safe_rcu(), must be either within an RCU read-side
294 critical section or must be protected by appropriate update-side
298 case the matching rcu_dereference() primitive must be used in
308 and you don't hold the appropriate update-side lock, you -must-
336 12. Any lock acquired by an RCU callback must be acquired elsewhere
348 must use whatever locking or other synchronization is required
386 srcu_read_unlock() calls must be passed the same srcu_struct.