Lines Matching full:memory

1 Kernel Memory Leak Detector
4 Kmemleak provides a way of detecting possible kernel memory leaks in a
9 Valgrind tool (``memcheck --leak-check``) to detect the memory leaks in
16 thread scans the memory every 10 minutes (by default) and prints the
22 To display the details of all the possible scanned memory leaks::
26 To trigger an intermediate memory scan::
30 To clear the list of all current possible memory leaks::
41 Memory scanning parameters can be modified at run-time by writing to the
51     start the automatic memory scanning thread (default)
53     stop the automatic memory scanning thread
55     set the automatic memory scanning period in seconds
58     trigger a memory scan
60     clear list of current memory leak suspects, done by
69 Memory may be allocated or freed before kmemleak is initialised and
83 The memory allocations via :c:func:`kmalloc`, :c:func:`vmalloc`,
90 An allocated block of memory is considered orphan if no pointer to its
92 scanning the memory (including saved registers). This means that there
95 memory leak.
101   2. scan the memory starting with the data section and stacks, checking
111 Some allocated memory blocks have pointers stored in the kernel's
141 To allow access to previously found memory leaks after kmemleak has been
144 a large part of physical memory.
146 In this situation, you may reclaim memory with::
156 - ``kmemleak_alloc``		 - notify of a memory block allocation
157 - ``kmemleak_alloc_percpu``	 - notify of a percpu memory block allocation
158 - ``kmemleak_vmalloc``		 - notify of a vmalloc() memory allocation
159 - ``kmemleak_free``		 - notify of a memory block freeing
160 - ``kmemleak_free_part``	 - notify of a partial memory block freeing
161 - ``kmemleak_free_percpu``	 - notify of a percpu memory block freeing
165 - ``kmemleak_scan_area``	 - add scan areas inside a memory block
166 - ``kmemleak_no_scan``	 - do not scan a memory block
182 The false negatives are real memory leaks (orphan objects) but not
183 reported by kmemleak because values found during the memory scanning
189 The false positives are objects wrongly reported as being memory leaks
192 the memory block is known not to contain other pointers and it will no
198 the minimum age of an object to be reported as a memory leak.
203 The main drawback is the reduced performance of memory allocation and
204 freeing. To avoid other penalties, the memory scanning is only performed
211 number of false negatives. However, it is likely that a real memory leak
230 module, a module that deliberately leaks memory. Set CONFIG_DEBUG_KMEMLEAK_TEST
239 memory leaks``. Then read the file to see then::