diff options
| author | Breno Leitao <leitao@debian.org> | 2026-09-17 06:47:35 -0700 |
|---|---|---|
| committer | Andrew Morton <akpm@linux-foundation.org> | 2026-10-12 21:26:25 -0700 |
| commit | 947ab1dd1c2d91c0d390e0008b6bfdc9a9d977b6 (patch) | |
| tree | dd1e688da1984ebb31610a31cd86d2e2868d4cf7 /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | e1012e4f37607fe451f0208fa5c2727923a8f966 (diff) | |
Documentation: kmemleak: describe the metadata pool, not the early log
Patch series "kmemleak: fix stale documentation and raise the verbose
default".
The first two patches fix statements in
Documentation/dev-tools/kmemleak.rst that do not match mm/kmemleak.c.
The third requires one more consecutive unreferenced scan before a
CONFIG_DEBUG_KMEMLEAK_VERBOSE kernel reports a leak on the console, to
avoid the last false positives I am seeing when running
CONFIG_DEBUG_KMEMLEAK_VERBOSE on a daily basis.
This patch (of 3):
commit c5665868183f ("mm: kmemleak: use the memory pool for early
allocations") removed the early log buffer in favour of a static pool of
kmemleak_object structures, but the documentation still describes the old
mechanism.
Fix the documentation by describing what the pool actually is, matching
the Kconfig help text.
Link: https://lore.kernel.org/20260917142210.90829-1-sj@kernel.org
Link: https://lore.kernel.org/20260917-b4-kmemleak-doc-v1-1-84fde6d1f749@debian.org
Fixes: c5665868183f ("mm: kmemleak: use the memory pool for early allocations")
Signed-off-by: Breno Leitao <leitao@debian.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Catalin Marinas <catalin.marinas@arm.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Randy Dunlap <rdunlap@infradead.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions
