summaryrefslogtreecommitdiffstats
path: root/Documentation
diff options
context:
space:
mode:
authorCatalin Marinas <catalin.marinas@arm.com>2009-06-26 17:38:26 +0100
committerCatalin Marinas <catalin.marinas@arm.com>2009-06-26 17:38:26 +0100
commitbab4a34afc301fdb81b6ea0e3098d96fc356e03a (patch)
treed9722d26dc944dbad1afd6dd182aa3a21907b96d /Documentation
parente0a2a1601bec01243bcad44414d06f59dae2eedb (diff)
downloadop-kernel-dev-bab4a34afc301fdb81b6ea0e3098d96fc356e03a.zip
op-kernel-dev-bab4a34afc301fdb81b6ea0e3098d96fc356e03a.tar.gz
kmemleak: Simplify the reports logged by the scanning thread
Because of false positives, the memory scanning thread may print too much information. This patch changes the scanning thread to only print the number of newly suspected leaks. Further information can be read from the /sys/kernel/debug/kmemleak file. Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/kmemleak.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/kmemleak.txt b/Documentation/kmemleak.txt
index 9426e94..c06f7ba 100644
--- a/Documentation/kmemleak.txt
+++ b/Documentation/kmemleak.txt
@@ -16,9 +16,9 @@ Usage
-----
CONFIG_DEBUG_KMEMLEAK in "Kernel hacking" has to be enabled. A kernel
-thread scans the memory every 10 minutes (by default) and prints any new
-unreferenced objects found. To trigger an intermediate scan and display
-all the possible memory leaks:
+thread scans the memory every 10 minutes (by default) and prints the
+number of new unreferenced objects found. To trigger an intermediate
+scan and display the details of all the possible memory leaks:
# mount -t debugfs nodev /sys/kernel/debug/
# cat /sys/kernel/debug/kmemleak
OpenPOWER on IntegriCloud