Searched refs:leaked (Results 1 – 17 of 17) sorted by relevance
551 bool *leaked) in __xenbus_map_ring() argument590 *leaked = false; in __xenbus_map_ring()593 *leaked = true; in __xenbus_map_ring()665 bool leaked = false; in xenbus_map_ring_hvm() local702 if (!leaked) in xenbus_map_ring_hvm()708 if (!leaked) in xenbus_map_ring_hvm()760 &leaked); in xenbus_map_ring_pv()777 if (!leaked) in xenbus_map_ring_pv()825 leaked = false; in xenbus_unmap_ring_pv()828 leaked = true; in xenbus_unmap_ring_pv()[all …]
48 result in sensitive information being leaked. Consider the following76 prevent information from being leaked via side-channels.
69 are not leaked (for example, in situations where a HIGHMEM page is in
550 so that a reservation will not be leaked when the huge page is freed.
1084 let (leaked, alloc) = Box::into_unique(b); in into_raw_with_allocator()1085 (leaked.as_ptr(), alloc) in into_raw_with_allocator()
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
76 be leaked. Only the victim is responsible for bringing data to the CPU. As
108 itself are not required because the necessary gadgets to expose the leaked
236 "EREMOVE returned ... and an EPC page was leaked. SGX may become unusable..."
240 and the other is a test whether the command leaked memory or not.
184 disk. This way, even if your ``.gnupg`` directory is leaked or stolen in286 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
270 leaked beyond the function boundary. This means that register
38 security-sensitive kernel-level state is leaked back to
71 access to buffers, via the leaked fd, to which it should otherwise
331 a leaked reference faster. A larger value may be useful to prevent false
24 3. Return leaked MPT frames to MPT command pool.
204 reference is not leaked, it is imperative to NULL-check the reference and in
Completed in 23 milliseconds