| /linux/drivers/xen/xenbus/ |
| H A D | xenbus_client.c | 561 bool *leaked) in __xenbus_map_ring() argument
600 *leaked = false; in __xenbus_map_ring()
603 *leaked = true; in __xenbus_map_ring()
676 bool leaked = false; in xenbus_map_ring_hvm() local
688 info, GNTMAP_host_map, &leaked); in xenbus_map_ring_hvm()
713 if (!leaked) in xenbus_map_ring_hvm()
719 if (!leaked) in xenbus_map_ring_hvm()
761 bool leaked = false; in xenbus_map_ring_pv() local
772 &leaked); in xenbus_map_ring_pv()
789 if (!leaked) in xenbus_map_ring_pv()
[all …]
|
| /linux/Documentation/staging/ |
| H A D | speculation.rst | 48 result in sensitive information being leaked. Consider the following
76 prevent information from being leaked via side-channels.
|
| /linux/drivers/xen/ |
| H A D | grant-table.c | 557 uint64_t leaked, deferred; in gnttab_add_deferred() local
581 leaked = atomic64_read(&leaked_count); in gnttab_add_deferred()
583 ref, page ? page_to_pfn(page) : -1, deferred, leaked); in gnttab_add_deferred()
586 leaked = atomic64_inc_return(&leaked_count); in gnttab_add_deferred()
588 ref, page ? page_to_pfn(page) : -1, deferred, leaked); in gnttab_add_deferred()
|
| /linux/Documentation/mm/ |
| H A D | balance.rst | 69 are not leaked (for example, in situations where a HIGHMEM page is in
|
| H A D | hugetlbfs_reserv.rst | 550 so that a reservation will not be leaked when the huge page is freed.
|
| /linux/tools/testing/selftests/tc-testing/ |
| H A D | README | 195 and the other is a test whether the command leaked memory or not.
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | spectre.rst | 164 accessed and leaked.
178 could cause privileged memory to be accessed and leaked.
209 If an attacker tries to control the memory addresses leaked during
|
| H A D | tsx_async_abort.rst | 76 be leaked. Only the victim is responsible for bringing data to the CPU. As
|
| /linux/Documentation/arch/x86/ |
| H A D | mds.rst | 111 itself are not required because the necessary gadgets to expose the leaked
|
| H A D | sgx.rst | 236 "EREMOVE returned ... and an EPC page was leaked. SGX may become unusable..."
|
| /linux/Documentation/process/ |
| H A D | maintainer-pgp-guide.rst | 184 disk. This way, even if your ``.gnupg`` directory is leaked or stolen in
286 think. They can be leaked or stolen via many different means:
367 Even though the Certify key is now safe from being leaked or stolen, the
|
| /linux/Documentation/security/tpm/ |
| H A D | tpm-security.rst | 109 during boot may have been leaked).
|
| /linux/security/ |
| H A D | Kconfig.hardening | 271 leaked beyond the function boundary. This means that register
|
| /linux/Documentation/driver-api/ |
| H A D | dma-buf.rst | 87 access to buffers, via the leaked fd, to which it should otherwise
|
| /linux/Documentation/admin-guide/sysctl/ |
| H A D | net.rst | 338 a leaked reference faster. A larger value may be useful to prevent false
|
| /linux/Documentation/scsi/ |
| H A D | ChangeLog.megaraid_sas | 24 3. Return leaked MPT frames to MPT command pool.
|
| /linux/fs/bcachefs/ |
| H A D | btree_iter.c | 3426 goto leaked; in check_btree_paths_leaked()
3428 leaked: in check_btree_paths_leaked()
|
| /linux/Documentation/RCU/ |
| H A D | checklist.rst | 493 combine with KASAN to check for pointers leaked out
|
| /linux/Documentation/bpf/ |
| H A D | verifier.rst | 204 reference is not leaked, it is imperative to NULL-check the reference and in
|