Searched refs:leaked (Results 1 – 17 of 17) sorted by relevance
| /Linux-v6.1/drivers/xen/xenbus/ |
| D | xenbus_client.c | 551 bool *leaked) in __xenbus_map_ring() argument
590 *leaked = false; in __xenbus_map_ring()
593 *leaked = true; in __xenbus_map_ring()
665 bool leaked = false; in xenbus_map_ring_hvm() local
677 info, GNTMAP_host_map, &leaked); in xenbus_map_ring_hvm()
702 if (!leaked) in xenbus_map_ring_hvm()
708 if (!leaked) in xenbus_map_ring_hvm()
749 bool leaked = false; in xenbus_map_ring_pv() local
760 &leaked); in xenbus_map_ring_pv()
777 if (!leaked) in xenbus_map_ring_pv()
[all …]
|
| /Linux-v6.1/Documentation/staging/ |
| D | speculation.rst | 48 result in sensitive information being leaked. Consider the following
76 prevent information from being leaked via side-channels.
|
| /Linux-v6.1/Documentation/mm/ |
| D | balance.rst | 71 are not leaked (for example, in situations where a HIGHMEM page is in
|
| D | hugetlbfs_reserv.rst | 551 so that a reservation will not be leaked when the huge page is freed.
|
| /Linux-v6.1/rust/alloc/ |
| D | boxed.rs | 1084 let (leaked, alloc) = Box::into_unique(b); in into_raw_with_allocator()
1085 (leaked.as_ptr(), alloc) in into_raw_with_allocator()
|
| /Linux-v6.1/Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 165 accessed and leaked.
179 could cause privileged memory to be accessed and leaked.
210 If an attacker tries to control the memory addresses leaked during
|
| D | tsx_async_abort.rst | 76 be leaked. Only the victim is responsible for bringing data to the CPU. As
|
| /Linux-v6.1/Documentation/x86/ |
| D | mds.rst | 108 itself are not required because the necessary gadgets to expose the leaked
|
| D | sgx.rst | 236 "EREMOVE returned ... and an EPC page was leaked. SGX may become unusable..."
|
| /Linux-v6.1/tools/testing/selftests/tc-testing/ |
| D | README | 240 and the other is a test whether the command leaked memory or not.
|
| /Linux-v6.1/Documentation/process/ |
| D | maintainer-pgp-guide.rst | 202 disk. This way, even if your ``.gnupg`` directory is leaked or stolen in
313 think. They can be leaked or stolen via many different means:
394 Even though the Certify key is now safe from being leaked or stolen, the
|
| /Linux-v6.1/security/ |
| D | Kconfig.hardening | 267 leaked beyond the function boundary. This means that register
|
| /Linux-v6.1/Documentation/ia64/ |
| D | fsys.rst | 38 security-sensitive kernel-level state is leaked back to
|
| /Linux-v6.1/Documentation/driver-api/ |
| D | dma-buf.rst | 71 access to buffers, via the leaked fd, to which it should otherwise
|
| /Linux-v6.1/Documentation/admin-guide/sysctl/ |
| D | net.rst | 325 a leaked reference faster. A larger value may be useful to prevent false
|
| /Linux-v6.1/Documentation/bpf/ |
| D | verifier.rst | 204 reference is not leaked, it is imperative to NULL-check the reference and in
|
| /Linux-v6.1/Documentation/scsi/ |
| D | ChangeLog.megaraid_sas | 24 3. Return leaked MPT frames to MPT command pool.
|
