Searched refs:splat (Results 1 – 6 of 6) sorted by relevance
11 When such misuse is detected, an lockdep-RCU splat is emitted.13 The usual cause of a lockdep-RCU splat is someone accessing an20 So let's look at an example RCU lockdep splat from 3.0-rc5, one that83 With this change, there would be no lockdep-RCU splat emitted if this86 the above lockdep-RCU splat because ->queue_lock is held (see #2 in the105 above lockdep-RCU splat.115 this change would also suppress the above lockdep-RCU splat.
1589 splat if rcu_dereference() is used outside of an RCU read-side1594 provided, a lockdep splat is emitted.1597 and emits a lockdep splat if neither rcu_read_lock() nor the1616 #. Kernels built with ``CONFIG_DEBUG_OBJECTS_RCU_HEAD=y`` will splat if1630 trigger an RCU CPU stall warning splat, with the duration of1634 is not obligated to produce this splat unless there is a grace period1953 offline CPUs. However, as a debugging measure, the FQS loop does splat2198 ``CONFIG_PROVE_RCU=y`` will splat if you try it.)2369 will result in a splat. It is therefore necessary to exercise caution
539 * foo bar splat
27 the validator will shoot a splat if incorrect.
1733 WARN_ONCE() splat.)
3596 will result in a splat once they do complete.5822 WARN_ONCE() splat and an ftrace_dump().