summaryrefslogtreecommitdiff
path: root/Documentation/kmemleak.txt
diff options
context:
space:
mode:
authorCatalin Marinas <catalin.marinas@arm.com>2009-08-27 14:29:15 +0100
committerCatalin Marinas <catalin.marinas@arm.com>2009-08-27 14:29:15 +0100
commit189d84ed54bbb05aac5b24d9d784d86c4d37f807 (patch)
tree6a856fddf93cd6688978d2d675623c96de4c46cd /Documentation/kmemleak.txt
parentaf98603dad87e393d2fc57117fe8a2aa6d620a0c (diff)
kmemleak: Dump object information on request
By writing dump=<addr> to the kmemleak file, kmemleak will look up an object with that address and dump the information it has about it to syslog. This is useful in debugging memory leaks. Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
Diffstat (limited to 'Documentation/kmemleak.txt')
-rw-r--r--Documentation/kmemleak.txt1
1 files changed, 1 insertions, 0 deletions
diff --git a/Documentation/kmemleak.txt b/Documentation/kmemleak.txt
index 89068030b01b..c223785339b5 100644
--- a/Documentation/kmemleak.txt
+++ b/Documentation/kmemleak.txt
@@ -42,6 +42,7 @@ Memory scanning parameters can be modified at run-time by writing to the
scan=<secs> - set the automatic memory scanning period in seconds
(default 600, 0 to stop the automatic scanning)
scan - trigger a memory scan
+ dump=<addr> - dump information about the object found at <addr>
Kmemleak can also be disabled at boot-time by passing "kmemleak=off" on
the kernel command line.