lkml.org 
[lkml]   [2019]   [Jul]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[PATCH 0/4] Lockdep: Reduce stack trace memory usage
Date
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(-)

--
2.22.0.657.g960e92d24f-goog

\
 
 \ /
  Last update: 2019-07-22 20:25    [W:0.098 / U:4.208 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site