| /kernel/linux/linux-5.10/samples/livepatch/ |
| D | livepatch-shadow-fix1.c | 56 int **leak = ctor_data; in shadow_leak_ctor() local
61 *shadow_leak = *leak; in shadow_leak_ctor()
68 int *leak; in livepatch_fix1_dummy_alloc() local
83 leak = kzalloc(sizeof(*leak), GFP_KERNEL); in livepatch_fix1_dummy_alloc()
84 if (!leak) in livepatch_fix1_dummy_alloc()
87 shadow_leak = klp_shadow_alloc(d, SV_LEAK, sizeof(leak), GFP_KERNEL, in livepatch_fix1_dummy_alloc()
88 shadow_leak_ctor, &leak); in livepatch_fix1_dummy_alloc()
91 __func__, d, leak); in livepatch_fix1_dummy_alloc()
101 kfree(leak); in livepatch_fix1_dummy_alloc()
|
| D | livepatch-shadow-mod.c | 98 int *leak; in dummy_alloc() local
108 leak = kzalloc(sizeof(*leak), GFP_KERNEL); in dummy_alloc()
109 if (!leak) { in dummy_alloc()
|
| /kernel/linux/linux-5.10/drivers/of/unittest-data/ |
| D | overlay_bad_add_dup_prop.dts | 17 * Modifying a property results in a WARNING that a memory leak
19 * fails, the memory leak does actually occur, and kmemleak will
20 * further report the memory leak if CONFIG_DEBUG_KMEMLEAK is
22 * memory leak and thus people who use kmemleak will not
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/ |
| D | power_domain.txt | 33 compatible = "foo,i-leak-current";
40 compatible = "foo,i-leak-current";
99 compatible = "foo,i-leak-current";
106 compatible = "foo,i-leak-current";
|
| /kernel/linux/linux-5.10/Documentation/dev-tools/ |
| D | kmemleak.rst | 9 Valgrind tool (``memcheck --leak-check``) to detect the memory leaks in
60 clear list of current memory leak suspects, done by
95 memory leak.
115 block is not considered a leak. One example is __vmalloc().
163 - ``kmemleak_not_leak`` - mark an object as not a leak
164 - ``kmemleak_ignore`` - do not scan or report an object as leak
199 the minimum age of an object to be reported as a memory leak.
212 number of false negatives. However, it is likely that a real memory leak
|
| /kernel/linux/linux-5.10/Documentation/features/debug/kmemleak/ |
| D | arch-support.txt | 4 # description: arch supports the kernel memory leak detector
|
| /kernel/linux/linux-5.10/net/rxrpc/ |
| D | conn_object.c | 461 bool leak = false; in rxrpc_destroy_all_connections() local
476 leak = true; in rxrpc_destroy_all_connections()
479 BUG_ON(leak); in rxrpc_destroy_all_connections()
|
| /kernel/linux/linux-5.10/Documentation/locking/ |
| D | percpu-rw-semaphore.rst | 21 The lock must be freed with percpu_free_rwsem to avoid memory leak.
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/freescale/fman/ |
| D | Kconfig | 22 internal resource leak thus stopping further packet processing.
|
| /kernel/linux/linux-5.10/arch/x86/ |
| D | Kconfig.debug | 104 allow to enable IOMMU leak tracing. Can be disabled at boot
114 bool "IOMMU leak tracing"
117 Add a simple leak tracer to the IOMMU code. This is useful when you
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | hpfs.rst | 231 0.92 Fixed a little memory leak in freeing directory inodes
235 0.94 Fixed a little memory leak when trying to delete busy file or directory
276 Fixed one buffer leak
290 1.95 Fixed one buffer leak, that could happen on corrupted filesystem
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | page_owner.rst | 11 It can be used to debug memory leak or to find a memory hogger.
|
| /kernel/linux/linux-5.10/drivers/infiniband/core/ |
| D | cache.c | 797 bool leak = false; in release_gid_table() local
810 leak = true; in release_gid_table()
813 if (leak) in release_gid_table()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/ |
| D | chosen.txt | 17 not be used for other purposes (as it may leak information about KASLR
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/Documentation/virt/kvm/ |
| D | s390-pv.rst | 84 instruction text, in order not to leak guest instruction text.
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/ |
| D | dm-crypt.rst | 107 the leak of information about the ciphertext device (filesystem type,
|
| /kernel/linux/linux-5.10/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 | 262 might allow a malicious actor to leak data from the host or from other
|
| /kernel/linux/linux-5.10/Documentation/driver-api/driver-model/ |
| D | devres.rst | 43 would leak resources or even cause oops when failure occurs. iomap
|
| /kernel/liteos_a/ |
| D | Kconfig | 268 …cord the LR of Function call stack of Mem operation, it can check the mem leak through the informa…
|
| /kernel/linux/linux-5.10/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.
|