| /Linux-v6.1/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()
|
| /Linux-v6.1/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
|
| /Linux-v6.1/lib/ |
| D | ref_tracker.c | 21 bool leak = false; in ref_tracker_dir_exit() local
34 leak = true; in ref_tracker_dir_exit()
39 WARN_ON_ONCE(leak); in ref_tracker_dir_exit()
|
| /Linux-v6.1/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";
|
| /Linux-v6.1/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
198 the minimum age of an object to be reported as a memory leak.
211 number of false negatives. However, it is likely that a real memory leak
|
| /Linux-v6.1/Documentation/features/debug/kmemleak/ |
| D | arch-support.txt | 4 # description: arch supports the kernel memory leak detector
|
| /Linux-v6.1/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-v6.1/Documentation/locking/ |
| D | percpu-rw-semaphore.rst | 21 The lock must be freed with percpu_free_rwsem to avoid memory leak.
|
| /Linux-v6.1/drivers/net/ethernet/freescale/fman/ |
| D | Kconfig | 22 internal resource leak thus stopping further packet processing.
|
| /Linux-v6.1/arch/x86/ |
| D | Kconfig.debug | 94 allow to enable IOMMU leak tracing. Can be disabled at boot
104 bool "IOMMU leak tracing"
107 Add a simple leak tracer to the IOMMU code. This is useful when you
|
| /Linux-v6.1/Documentation/filesystems/ext4/ |
| D | orphan.rst | 9 would leak. Similarly if we truncate or extend the file, we need not be able
|
| /Linux-v6.1/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
|
| D | fuse.rst | 241 counts as an information leak.
312 information leak or *DoS* as described in points B and C/2/i-ii in the
|
| /Linux-v6.1/Documentation/security/ |
| D | landlock.rst | 37 * To avoid multiple kinds of side-channel attacks (e.g. leak of security
|
| /Linux-v6.1/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()
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | nvmem.rst | 25 was a rather big abstraction leak.
|
| D | isa.rst | 53 internal to the bus it's much cleaner to not leak isa_dev's by passing
|
| /Linux-v6.1/Documentation/admin-guide/hw-vuln/ |
| D | core-scheduling.rst | 144 in the case of guests. At best, this would only leak some scheduler metadata
179 starts to run and this is a possibility for data leak.
|
| 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
|
| /Linux-v6.1/Documentation/virt/kvm/s390/ |
| D | s390-pv.rst | 84 instruction text, in order not to leak guest instruction text.
|
| /Linux-v6.1/Documentation/admin-guide/device-mapper/ |
| D | dm-crypt.rst | 107 the leak of information about the ciphertext device (filesystem type,
|
| /Linux-v6.1/rust/alloc/ |
| D | boxed.rs | 1103 (Unique::from(Box::leak(b)), alloc) in into_unique()
1156 pub const fn leak<'a>(b: Self) -> &'a mut T in leak() method
|
| /Linux-v6.1/Documentation/process/ |
| D | researcher-guidelines.rst | 104 would result in a 64 byte slab memory leak once per device attach,
|
| /Linux-v6.1/Documentation/mm/ |
| D | page_owner.rst | 11 It can be used to debug memory leak or to find a memory hogger.
|
