RCU debug-objects improvements
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | rcu: Simplify debug-objects fixupskernel/ | +0 | 0 replies | |
| 2/4 | debugobjects: Make debug_object_activate() return statusinclude/ lib/ | +17 | 0 replies | |
| 3/4 | rcu: Make call_rcu() leak callbacks for debug-object errorskernel/ kernel/ | +20 | 0 replies | |
| 4/4 | rcu: Add duplicate-callback tests to rcutorturekernel/ | +37 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH tip/core/rcu 0/4] RCU debug-objects improvements
Hello!
RCU's current debug-objects fixups are complex and heavyweight, plus the fixups are not complete, because even with the fixups, RCU's callback lists can still be corrupted. This series reworks RCU's use of the debug-objects facility and the facility itself to allow improved handling of things like duplicate invocations of call_rcu(). This series includes:
1. Simplify RCU's debug-objects fixups.
2. Make debug_object_activate() return status.
3. Make __call_rcu() leak callbacks when debug_object_activate()
notes suspicious activity. Leaking has its problems, but it is far better than silent corruption of RCU's data structures.
4. Add a new object_debug option to rcutorture to allow
deterministic testing of #3 above.
Thanx, Paul
b/include/linux/debugobjects.h | 6 +- b/kernel/rcu.h | 10 ++-- b/kernel/rcupdate.c | 100 ----------------------------------------- b/kernel/rcutorture.c | 37 +++++++++++++++ b/kernel/rcutree.c | 14 +++++ b/lib/debugobjects.c | 20 +++++--- 6 files changed, 74 insertions(+), 113 deletions(-)