Commit bf96d1e3e7a35a17cea255048ffb3243bd9c8123
1 parent
ae281064be
kmemleak: Do not force the slab debugging Kconfig options
Selecting DEBUG_SLAB or SLUB_DEBUG by the KMEMLEAK menu entry may cause issues with other dependencies (KMEMCHECK). These configuration options aren't strictly needed by kmemleak but they may increase the chances of finding leaks. This patch also updates the KMEMLEAK config entry help text. Signed-off-by: Catalin Marinas <catalin.marinas@arm.com> Acked-by: Pekka Enberg <penberg@cs.helsinki.fi>
Showing 1 changed file with 3 additions and 2 deletions Side-by-side Diff
lib/Kconfig.debug
| ... | ... | @@ -340,8 +340,6 @@ |
| 340 | 340 | bool "Kernel memory leak detector" |
| 341 | 341 | depends on DEBUG_KERNEL && EXPERIMENTAL && (X86 || ARM) && \ |
| 342 | 342 | !MEMORY_HOTPLUG |
| 343 | - select DEBUG_SLAB if SLAB | |
| 344 | - select SLUB_DEBUG if SLUB | |
| 345 | 343 | select DEBUG_FS if SYSFS |
| 346 | 344 | select STACKTRACE if STACKTRACE_SUPPORT |
| 347 | 345 | select KALLSYMS |
| ... | ... | @@ -354,6 +352,9 @@ |
| 354 | 352 | feature will introduce an overhead to memory |
| 355 | 353 | allocations. See Documentation/kmemleak.txt for more |
| 356 | 354 | details. |
| 355 | + | |
| 356 | + Enabling DEBUG_SLAB or SLUB_DEBUG may increase the chances | |
| 357 | + of finding leaks due to the slab objects poisoning. | |
| 357 | 358 | |
| 358 | 359 | In order to access the kmemleak file, debugfs needs to be |
| 359 | 360 | mounted (usually at /sys/kernel/debug). |