Lockdep: Reduce stack trace memory usage
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | locking/lockdep: Make it clear that what lock_class::key points at is not modifiedinclude/ kernel/ kernel/ +1 more | +5 | 0 replies | |
| 2/4 | stacktrace: Constify 'entries' argumentsinclude/ kernel/ | +4 | 0 replies | |
| 3/4 | locking/lockdep: Reduce space occupied by stack tracesinclude/ kernel/ kernel/ | +95 | 2 replies | |
| 4/4 | locking/lockdep: Report more stack trace statisticskernel/ kernel/ kernel/ | +39 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] Lockdep: Reduce stack trace memory usage
Hi Peter,
An unfortunate side effect of commit 669de8bda87b ("kernel/workqueue: Use dynamic lockdep keys for workqueues") is that all stack traces associated with the lockdep key are leaked when a workqueue is destroyed. Fix this by storing each unique stack trace once. Please consider this patch series for Linux kernel v5.4.
Thanks,
Bart.
Bart Van Assche (4):
locking/lockdep: Make it clear that what lock_class::key points at is
not modified
stacktrace: Constify 'entries' arguments
locking/lockdep: Reduce space occupied by stack traces locking/lockdep: Report more stack trace statistics
include/linux/lockdep.h | 11 +- include/linux/stacktrace.h | 4 +- kernel/locking/lockdep.c | 159 ++++++++++++++++++++++------- kernel/locking/lockdep_internals.h | 9 +- kernel/locking/lockdep_proc.c | 8 +- kernel/stacktrace.c | 4 +- 6 files changed, 143 insertions(+), 52 deletions(-)
Signature · 1 line
2.22.0.657.g960e92d24f-goog