| /linux/samples/livepatch/ |
| H A 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 82 leak = kzalloc(sizeof(*leak), GFP_KERNEL); in livepatch_fix1_dummy_alloc() 83 if (!leak) in livepatch_fix1_dummy_alloc() 86 shadow_leak = klp_shadow_alloc(d, SV_LEAK, sizeof(leak), GFP_KERNEL, in livepatch_fix1_dummy_alloc() 87 shadow_leak_ctor, &leak); in livepatch_fix1_dummy_alloc() 90 __func__, d, leak); in livepatch_fix1_dummy_alloc() 100 kfree(leak); in livepatch_fix1_dummy_alloc()
|
| /linux/drivers/of/unittest-data/ |
| H A D | overlay_bad_add_dup_prop.dtso | 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/Documentation/devicetree/bindings/power/ |
| H A 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/Documentation/features/debug/kmemleak/ |
| H A D | arch-support.txt | 4 # description: arch supports the kernel memory leak detector
|
| /linux/net/rxrpc/ |
| H A D | conn_object.c | 469 bool leak = false; in rxrpc_destroy_all_connections() local 483 leak = true; in rxrpc_destroy_all_connections() 486 BUG_ON(leak); in rxrpc_destroy_all_connections()
|
| /linux/drivers/gpu/drm/ci/xfails/ |
| H A D | i915-apl-flakes.txt | 13 kms_universal_plane@cursor-fb-leak
|
| /linux/lib/ |
| H A D | ref_tracker.c | 223 bool leak = false; in ref_tracker_dir_exit() local 239 leak = true; in ref_tracker_dir_exit() 246 WARN_ON_ONCE(leak); in ref_tracker_dir_exit()
|
| /linux/scripts/ |
| H A D | git-resolve.sh | 110 …'--force 99999999 ("net/tls: Fix skb memory leak when running kTLS traffic")' # Force mode with n…
|
| /linux/drivers/net/ethernet/freescale/fman/ |
| H A D | Kconfig | 23 internal resource leak thus stopping further packet processing.
|
| /linux/Documentation/translations/zh_CN/process/ |
| H A D | researcher-guidelines.rst | 97 would result in a 64 byte slab memory leak once per device attach,
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | orphan.rst | 9 would leak. Similarly if we truncate or extend the file, we need not be able
|
| /linux/Documentation/translations/zh_CN/dev-tools/ |
| H A D | kmemleak.rst | 14 (``memcheck --leak-check``)使用了一种相似的方法来检测用户空间应用中的内存泄
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | attack_vector_controls.rst | 35 attempting to leak kernel data into userspace by exploiting a CPU vulnerability. 74 The guest-to-host attack vector involves a malicious VM attempting to leak
|
| H A 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.
|
| H A 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/Documentation/hwmon/ |
| H A D | aquacomputer_d5next.rst | 15 * Aquacomputer Leakshield leak prevention system
|
| /linux/Documentation/driver-api/ |
| H A D | isa.rst | 53 internal to the bus it's much cleaner to not leak isa_dev's by passing
|
| H A D | nvmem.rst | 25 was a rather big abstraction leak.
|
| /linux/Documentation/virt/kvm/s390/ |
| H A D | s390-pv.rst | 84 instruction text, in order not to leak guest instruction text.
|
| /linux/rust/kernel/alloc/ |
| H A D | kbox.rs | 209 pub fn leak<'a>(b: Self) -> &'a mut T { 211 pub fn leak<'a>(b: Self) -> &'a mut T { leak() function
|
| /linux/Documentation/filesystems/fuse/ |
| H A D | fuse.rst | 255 counts as an information leak. 326 information leak or *DoS* as described in points B and C/2/i-ii in the
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-crypt.rst | 107 the leak of information about the ciphertext device (filesystem type,
|
| /linux/Documentation/translations/sp_SP/process/ |
| H A D | researcher-guidelines.rst | 111 would result in a 64 byte slab memory leak once per device attach,
|
| /linux/Documentation/process/ |
| H A D | researcher-guidelines.rst | 131 would result in a 64 byte slab memory leak once per device attach,
|
| /linux/Documentation/scsi/ |
| H A 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.
|