| /Linux-v4.19/samples/livepatch/ |
| D | livepatch-shadow-fix1.c | 68 void *leak = ctor_data; in shadow_leak_ctor() local
70 *shadow_leak = leak; in shadow_leak_ctor()
77 void *leak; in livepatch_fix1_dummy_alloc() local
91 leak = kzalloc(sizeof(int), GFP_KERNEL); in livepatch_fix1_dummy_alloc()
92 klp_shadow_alloc(d, SV_LEAK, sizeof(leak), GFP_KERNEL, in livepatch_fix1_dummy_alloc()
93 shadow_leak_ctor, leak); in livepatch_fix1_dummy_alloc()
|
| D | livepatch-shadow-mod.c | 110 void *leak; in dummy_alloc() local
120 leak = kzalloc(sizeof(int), GFP_KERNEL); in dummy_alloc()
|
| /Linux-v4.19/Documentation/dev-tools/ |
| D | kmemleak.rst | 9 Valgrind tool (``memcheck --leak-check``) to detect the memory leaks in
58 clear list of current memory leak suspects, done by
90 memory leak.
110 block is not considered a leak. One example is __vmalloc().
158 - ``kmemleak_not_leak`` - mark an object as not a leak
159 - ``kmemleak_ignore`` - do not scan or report an object as leak
194 the minimum age of an object to be reported as a memory leak.
207 number of false negatives. However, it is likely that a real memory leak
|
| /Linux-v4.19/Documentation/devicetree/bindings/power/ |
| D | power_domain.txt | 126 compatible = "foo,i-leak-current";
133 compatible = "foo,i-leak-current";
192 compatible = "foo,i-leak-current";
199 compatible = "foo,i-leak-current";
|
| /Linux-v4.19/net/rxrpc/ |
| D | conn_object.c | 462 bool leak = false; in rxrpc_destroy_all_connections() local
477 leak = true; in rxrpc_destroy_all_connections()
480 BUG_ON(leak); in rxrpc_destroy_all_connections()
|
| /Linux-v4.19/Documentation/ |
| D | percpu-rw-semaphore.txt | 21 The lock must be freed with percpu_free_rwsem to avoid memory leak.
|
| D | isa.txt | 53 internal to the bus it's much cleaner to not leak isa_dev's by passing
|
| /Linux-v4.19/Documentation/x86/x86_64/ |
| D | boot-options.txt | 212 iommu=[<size>][,noagp][,off][,force][,noforce][,leak[=<nr_of_leak_pages>]
231 leak Turn on simple iommu leak tracing (only when
232 CONFIG_IOMMU_LEAK is on). Default number of leak pages
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | hpfs.txt | 212 0.92 Fixed a little memory leak in freeing directory inodes
216 0.94 Fixed a little memory leak when trying to delete busy file or directory
243 Fixed one buffer leak
252 1.95 Fixed one buffer leak, that could happen on corrupted filesystem
|
| /Linux-v4.19/arch/x86/ |
| D | Kconfig.debug | 163 allow to enable IOMMU leak tracing. Can be disabled at boot
173 bool "IOMMU leak tracing"
176 Add a simple leak tracer to the IOMMU code. This is useful when you
|
| /Linux-v4.19/Documentation/vm/ |
| D | page_owner.rst | 11 It can be used to debug memory leak or to find a memory hogger.
|
| /Linux-v4.19/drivers/infiniband/core/ |
| D | cache.c | 775 bool leak = false; in release_gid_table() local
788 leak = true; in release_gid_table()
791 if (leak) in release_gid_table()
|
| /Linux-v4.19/Documentation/devicetree/bindings/ |
| D | chosen.txt | 17 not be used for other purposes (as it may leak information about KASLR
|
| /Linux-v4.19/Documentation/nvmem/ |
| D | nvmem.txt | 20 was a rather big abstraction leak.
|
| /Linux-v4.19/Documentation/ide/ |
| D | ChangeLog.ide-cd.1994-2004 | 46 * Fix usage count leak in cdrom_open, which happened
153 * -- Fixed a memory leak where info->changer_info was
|
| /Linux-v4.19/Documentation/driver-api/ |
| D | dma-buf.rst | 69 on the file descriptor. This is not just a resource leak, but a
|
| /Linux-v4.19/Documentation/device-mapper/ |
| D | dm-crypt.txt | 96 the leak of information about the ciphertext device (filesystem type,
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | l1tf.rst | 194 interesting data to an attacker, but they can leak information about the
428 VMENTER can leak host memory which is considered
429 interesting for an attacker. This still can leak host memory
|
| /Linux-v4.19/Documentation/driver-model/ |
| D | devres.txt | 41 would leak resources or even cause oops when failure occurs. iomap
|
| /Linux-v4.19/Documentation/scsi/ |
| D | ChangeLog.lpfc | 129 * Close humongous memory leak in lpfc_sli.c - driver was losing 13
144 * Fixed a memory leak of iocbq structure. For ELS solicited iocbs
146 * Closed large memory leak -- we were losing 13 iocbq structures
304 * Fix leak of "host" in the error path in the remove_one() path.
373 memory leak
1080 leak.
1353 * Fix IOCB memory leak
1684 * Moving fix for memory leak in ioctl lip area to sysfs's lip.
|
| /Linux-v4.19/arch/arm64/ |
| D | Kconfig | 897 be used to bypass MMU permission checks and leak kernel data to
922 bool "Harden EL2 vector mapping against system register leak" if EXPERT
926 be used to leak privileged information such as the vector base
1213 to leak information about the location of core kernel data structures
|
| /Linux-v4.19/drivers/gpu/drm/ |
| D | Kconfig | 45 Enable allocation tracking of memory manager and leak detection on
|
| /Linux-v4.19/Documentation/RCU/ |
| D | checklist.txt | 68 Letting RCU-protected pointers "leak" out of an RCU read-side
69 critical section is every bid as bad as letting them leak out
|
| /Linux-v4.19/Documentation/ia64/ |
| D | fsys.txt | 142 o Fsyscall-handlers must be careful not to leak sensitive kernel'
|
| /Linux-v4.19/Documentation/i2c/ |
| D | i2c-topology | 223 issues any unlocked i2c transfers on the root adapter that may leak
|
