Searched refs:leaked (Results 1 – 10 of 10) sorted by relevance
/Linux-v4.19/drivers/xen/xenbus/ |
D | xenbus_client.c | 466 bool *leaked) in __xenbus_map_ring() argument 511 *leaked = false; in __xenbus_map_ring() 514 *leaked = true; in __xenbus_map_ring() 553 bool leaked = false; in xenbus_map_ring_valloc_hvm() local 577 info.phys_addrs, GNTMAP_host_map, &leaked); in xenbus_map_ring_valloc_hvm() 600 if (!leaked) in xenbus_map_ring_valloc_hvm() 606 if (!leaked) in xenbus_map_ring_valloc_hvm() 635 unsigned long *vaddrs, bool *leaked) in xenbus_map_ring() argument 647 phys_addrs, GNTMAP_host_map, leaked); in xenbus_map_ring() 682 bool leaked; in xenbus_map_ring_valloc_pv() local [all …]
|
/Linux-v4.19/Documentation/ |
D | speculation.txt | 46 result in sensitive information being leaked. Consider the following 74 prevent information from being leaked via side-channels.
|
/Linux-v4.19/include/xen/ |
D | xenbus.h | 211 bool *leaked);
|
/Linux-v4.19/Documentation/driver-api/ |
D | dma-buf.rst | 71 access to buffers, via the leaked fd, to which it should otherwise
|
/Linux-v4.19/Documentation/vm/ |
D | balance.rst | 71 are not leaked (for example, in situations where a HIGHMEM page is in
|
D | hugetlbfs_reserv.rst | 550 so that a reservation will not be leaked when the huge page is freed.
|
/Linux-v4.19/tools/testing/selftests/tc-testing/ |
D | README | 232 and the other is a test whether the command leaked memory or not.
|
/Linux-v4.19/Documentation/process/ |
D | maintainer-pgp-guide.rst | 206 disk. This way, even if your ``.gnupg`` directory is leaked or stolen in 323 think. They can be leaked or stolen via many different means: 404 Even though the master key is now safe from being leaked or stolen, the
|
/Linux-v4.19/Documentation/ia64/ |
D | fsys.txt | 38 security-sensitive kernel-level state is leaked back to
|
/Linux-v4.19/Documentation/scsi/ |
D | ChangeLog.megaraid_sas | 24 3. Return leaked MPT frames to MPT command pool.
|