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
17 thread scans the memory every 10 minutes (by default) and prints the
23 To display the details of all the possible scanned memory leaks::
27 To trigger an intermediate memory scan::
31 To clear the list of all current possible memory leaks::
42 Memory scanning parameters can be modified at run-time by writing to the
52     start the automatic memory scanning thread (default)
54     stop the automatic memory scanning thread
56     set the automatic memory scanning period in seconds
59     trigger a memory scan
61     clear list of current memory leak suspects, done by
70 Memory may be allocated or freed before kmemleak is initialised and
84 The memory allocations via :c:func:`kmalloc`, :c:func:`vmalloc`,
91 An allocated block of memory is considered orphan if no pointer to its
93 scanning the memory (including saved registers). This means that there
96 memory leak.
102   2. scan the memory starting with the data section and stacks, checking
112 Some allocated memory blocks have pointers stored in the kernel's
142 To allow access to previously found memory leaks after kmemleak has been
145 a large part of physical memory.
147 In this situation, you may reclaim memory with::
157 - ``kmemleak_alloc``		 - notify of a memory block allocation
158 - ``kmemleak_alloc_percpu``	 - notify of a percpu memory block allocation
159 - ``kmemleak_vmalloc``		 - notify of a vmalloc() memory allocation
160 - ``kmemleak_free``		 - notify of a memory block freeing
161 - ``kmemleak_free_part``	 - notify of a partial memory block freeing
162 - ``kmemleak_free_percpu``	 - notify of a percpu memory block freeing
166 - ``kmemleak_scan_area``	 - add scan areas inside a memory block
167 - ``kmemleak_no_scan``	 - do not scan a memory block
184 The false negatives are real memory leaks (orphan objects) but not
185 reported by kmemleak because values found during the memory scanning
191 The false positives are objects wrongly reported as being memory leaks
194 the memory block is known not to contain other pointers and it will no
200 the minimum age of an object to be reported as a memory leak.
205 The main drawback is the reduced performance of memory allocation and
206 freeing. To avoid other penalties, the memory scanning is only performed
213 number of false negatives. However, it is likely that a real memory leak
232 module, a module that deliberately leaks memory. Set CONFIG_DEBUG_KMEMLEAK_TEST
241 memory leaks``. Then read the file to see then::