RFC using lockdep to validate rcu usage
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest6 patches 23 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/6 | lockdep: annotate rcu_read_{,un}lock{,_bh}include/ include/ kernel/ | +29 | 1 reply | |
| 2/6 | lockdep: validate rcu_dereference() vs rcu_read_lock()include/ include/ kernel/ | +67 | 21 replies | |
| 3/6 | lockdep: rcu_dereference() vs preempt_disable()include/ kernel/ lib/ | +22 | 0 replies | |
| 4/6 | implicit vs explicit preempt_disable()include/ kernel/ kernel/ +1 more | +82 | 0 replies | |
| 5/6 | fixup funny preemption tricks in irq_exitkernel/ | +1 | 0 replies | |
| 6/6 | fixup early bootinit/ | +3 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 0/6] using lockdep to validate rcu usage
This patch set uses lockdep to validate rcu usage.
It annotates rcu_read_{,un}lock{,_bh}() to catch imbalances. And further uses that information to establish a proper context for rcu_dereference().
It also separates implicit from explicit preempt_disable() usage, in order to separate rcu_dereference() from the locking model.
A kernel (2.6.23-rc4-mm1) with these patches boots but does have some funnies - I suspect it calls printf from places it doesn't like.
The first patch should be safe to apply, the rest is RFC.
If people want to see the very noisy bootlog this generates:
http://programming.kicks-ass.net/kernel-patches/lockdep_rcu/lockdep_rcu.log