| /Linux-v5.4/samples/livepatch/ |
| D | livepatch-shadow-fix1.c | 56 void *leak = ctor_data; in shadow_leak_ctor() local
58 *shadow_leak = leak; in shadow_leak_ctor()
65 void *leak; in livepatch_fix1_dummy_alloc() local
79 leak = kzalloc(sizeof(int), GFP_KERNEL); in livepatch_fix1_dummy_alloc()
80 if (!leak) { in livepatch_fix1_dummy_alloc()
85 klp_shadow_alloc(d, SV_LEAK, sizeof(leak), GFP_KERNEL, in livepatch_fix1_dummy_alloc()
86 shadow_leak_ctor, leak); in livepatch_fix1_dummy_alloc()
|
| D | livepatch-shadow-mod.c | 98 void *leak; in dummy_alloc() local
108 leak = kzalloc(sizeof(int), GFP_KERNEL); in dummy_alloc()
109 if (!leak) { in dummy_alloc()
|
| /Linux-v5.4/Documentation/dev-tools/ |
| D | kmemleak.rst | 9 Valgrind tool (``memcheck --leak-check``) to detect the memory leaks in
61 clear list of current memory leak suspects, done by
96 memory leak.
116 block is not considered a leak. One example is __vmalloc().
164 - ``kmemleak_not_leak`` - mark an object as not a leak
165 - ``kmemleak_ignore`` - do not scan or report an object as leak
200 the minimum age of an object to be reported as a memory leak.
213 number of false negatives. However, it is likely that a real memory leak
|
| /Linux-v5.4/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";
|
| D | qcom,rpmpd.txt | 118 compatible = "foo,i-leak-current";
|
| /Linux-v5.4/drivers/staging/exfat/ |
| D | TODO | 1 exfat_core.c - ffsReadFile - the goto err_out seem to leak a brelse().
|
| /Linux-v5.4/net/rxrpc/ |
| D | conn_object.c | 460 bool leak = false; in rxrpc_destroy_all_connections() local
475 leak = true; in rxrpc_destroy_all_connections()
478 BUG_ON(leak); in rxrpc_destroy_all_connections()
|
| /Linux-v5.4/Documentation/ |
| D | percpu-rw-semaphore.txt | 21 The lock must be freed with percpu_free_rwsem to avoid memory leak.
|
| /Linux-v5.4/arch/x86/ |
| D | Kconfig.debug | 153 allow to enable IOMMU leak tracing. Can be disabled at boot
163 bool "IOMMU leak tracing"
166 Add a simple leak tracer to the IOMMU code. This is useful when you
|
| /Linux-v5.4/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-v5.4/Documentation/vm/ |
| D | page_owner.rst | 11 It can be used to debug memory leak or to find a memory hogger.
|
| /Linux-v5.4/drivers/infiniband/core/ |
| D | cache.c | 794 bool leak = false; in release_gid_table() local
807 leak = true; in release_gid_table()
810 if (leak) in release_gid_table()
|
| /Linux-v5.4/Documentation/devicetree/bindings/ |
| D | chosen.txt | 17 not be used for other purposes (as it may leak information about KASLR
|
| /Linux-v5.4/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-v5.4/Documentation/driver-api/ |
| D | isa.rst | 53 internal to the bus it's much cleaner to not leak isa_dev's by passing
|
| D | nvmem.rst | 25 was a rather big abstraction leak.
|
| D | dma-buf.rst | 69 on the file descriptor. This is not just a resource leak, but a
|
| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| D | dm-crypt.rst | 107 the leak of information about the ciphertext device (filesystem type,
|
| /Linux-v5.4/Documentation/admin-guide/hw-vuln/ |
| D | l1tf.rst | 194 interesting data to an attacker, but they can leak information about the
431 VMENTER can leak host memory which is considered
432 interesting for an attacker. This still can leak host memory
|
| D | tsx_async_abort.rst | 261 might allow a malicious actor to leak data from the host or from other
|
| /Linux-v5.4/Documentation/driver-api/driver-model/ |
| D | devres.rst | 43 would leak resources or even cause oops when failure occurs. iomap
|
| /Linux-v5.4/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-v5.4/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-v5.4/arch/arm64/ |
| D | Kconfig | 1076 be used to bypass MMU permission checks and leak kernel data to
1101 bool "Harden EL2 vector mapping against system register leak" if EXPERT
1105 be used to leak privileged information such as the vector base
1562 to leak information about the location of core kernel data structures
|
| /Linux-v5.4/drivers/gpu/drm/ |
| D | Kconfig | 50 Enable allocation tracking of memory manager and leak detection on
|
