diff options
| author | Stephen Rothwell <sfr@canb.auug.org.au> | 2009-08-18 15:31:35 +1000 |
|---|---|---|
| committer | Stephen Rothwell <sfr@canb.auug.org.au> | 2009-08-18 15:31:35 +1000 |
| commit | 8a2fe3a077671738a784311eeed40c4650b287d1 (patch) | |
| tree | 29da29b1f45c5b97565577424dc572dc17c975da /Documentation | |
| parent | 093640e33cfacdb8616ed4fc05de26aaf6102dd6 (diff) | |
| parent | 55923ccd900d84568e2731f915dd5188b6ea5f33 (diff) | |
Merge commit 'kmemleak/kmemleak'
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/kmemleak.txt | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/Documentation/kmemleak.txt b/Documentation/kmemleak.txt index 89068030b01b..fa932490b3dc 100644 --- a/Documentation/kmemleak.txt +++ b/Documentation/kmemleak.txt @@ -35,13 +35,12 @@ Memory scanning parameters can be modified at run-time by writing to the /sys/kernel/debug/kmemleak file. The following parameters are supported: off - disable kmemleak (irreversible) - stack=on - enable the task stacks scanning (default) - stack=off - disable the tasks stacks scanning scan=on - start the automatic memory scanning thread (default) scan=off - stop the automatic memory scanning thread 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. @@ -110,7 +109,8 @@ reported by kmemleak because values found during the memory scanning point to such objects. To reduce the number of false negatives, kmemleak provides the kmemleak_ignore, kmemleak_scan_area, kmemleak_no_scan and kmemleak_erase functions (see above). The task stacks also increase the -amount of false negatives and their scanning is not enabled by default. +amount of false negatives (enabling CONFIG_DEBUG_STACK_USAGE would help +by zeroing newly allocated stacks). The false positives are objects wrongly reported as being memory leaks (orphan). For objects known not to be leaks, kmemleak provides the @@ -119,9 +119,9 @@ the memory block is known not to contain other pointers and it will no longer be scanned. Some of the reported leaks are only transient, especially on SMP -systems, because of pointers temporarily stored in CPU registers or -stacks. Kmemleak defines MSECS_MIN_AGE (defaulting to 1000) representing -the minimum age of an object to be reported as a memory leak. +systems, because of pointers temporarily stored in CPU registers. +Kmemleak defines MSECS_MIN_AGE (defaulting to 5000) representing the +minimum age of an object to be reported as a memory leak. Limitations and Drawbacks ------------------------- |