Searched refs:leaked (Results 1 – 14 of 14) sorted by relevance
| /Linux-v5.4/drivers/xen/xenbus/ |
| D | xenbus_client.c | 464 bool *leaked) in __xenbus_map_ring() argument
509 *leaked = false; in __xenbus_map_ring()
512 *leaked = true; in __xenbus_map_ring()
551 bool leaked = false; in xenbus_map_ring_valloc_hvm() local
575 info.phys_addrs, GNTMAP_host_map, &leaked); in xenbus_map_ring_valloc_hvm()
598 if (!leaked) in xenbus_map_ring_valloc_hvm()
604 if (!leaked) in xenbus_map_ring_valloc_hvm()
633 unsigned long *vaddrs, bool *leaked) in xenbus_map_ring() argument
645 phys_addrs, GNTMAP_host_map, leaked); in xenbus_map_ring()
680 bool leaked; in xenbus_map_ring_valloc_pv() local
[all …]
|
| /Linux-v5.4/Documentation/ |
| D | speculation.txt | 46 result in sensitive information being leaked. Consider the following
74 prevent information from being leaked via side-channels.
|
| /Linux-v5.4/include/xen/ |
| D | xenbus.h | 211 bool *leaked);
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | dma-buf.rst | 71 access to buffers, via the leaked fd, to which it should otherwise
|
| /Linux-v5.4/Documentation/vm/ |
| 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-v5.4/Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 152 accessed and leaked.
166 could cause privileged memory to be accessed and leaked.
197 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-v5.4/Documentation/x86/ |
| D | mds.rst | 108 itself are not required because the necessary gadgets to expose the leaked
|
| /Linux-v5.4/tools/testing/selftests/tc-testing/ |
| D | README | 240 and the other is a test whether the command leaked memory or not.
|
| /Linux-v5.4/Documentation/process/ |
| D | maintainer-pgp-guide.rst | 206 disk. This way, even if your ``.gnupg`` directory is leaked or stolen in
326 think. They can be leaked or stolen via many different means:
407 Even though the master key is now safe from being leaked or stolen, the
|
| /Linux-v5.4/Documentation/ia64/ |
| D | fsys.rst | 38 security-sensitive kernel-level state is leaked back to
|
| /Linux-v5.4/Documentation/scsi/ |
| D | ChangeLog.megaraid_sas | 24 3. Return leaked MPT frames to MPT command pool.
|
| /Linux-v5.4/Documentation/networking/ |
| D | filter.txt | 1192 reference is not leaked, it is imperative to NULL-check the reference and in
|
