Searched refs:leaked (Results 1 – 12 of 12) sorted by relevance
568 bool *leaked) in __xenbus_map_ring() argument607 *leaked = false; in __xenbus_map_ring()610 *leaked = true; in __xenbus_map_ring()683 bool leaked = false; in xenbus_map_ring_hvm() local695 info, GNTMAP_host_map, &leaked); in xenbus_map_ring_hvm()720 if (!leaked) in xenbus_map_ring_hvm()726 if (!leaked) in xenbus_map_ring_hvm()768 bool leaked = false; in xenbus_map_ring_pv() local779 &leaked); in xenbus_map_ring_pv()796 if (!leaked) in xenbus_map_ring_pv()[all …]
48 result in sensitive information being leaked. Consider the following75 prevent information from being leaked via side-channels.
1830 int leaked; in qman_destroy_fq() local1845 leaked = qman_shutdown_fq(fq->fqid); in qman_destroy_fq()1846 if (leaked) in qman_destroy_fq()1853 if (fq_isset(fq, QMAN_FQ_FLAG_DYNAMIC_FQID) && !leaked) { in qman_destroy_fq()
195 and the other is a test whether the command leaked memory or not.
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
76 be leaked. Only the victim is responsible for bringing data to the CPU. As
111 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..."
109 during boot may have been leaked).
359 a leaked reference faster. A larger value may be useful to prevent false
24 3. Return leaked MPT frames to MPT command pool.
506 combine with KASAN to check for pointers leaked out