Searched refs:leaked (Results 1 – 14 of 14) sorted by relevance
| /linux/drivers/xen/xenbus/ |
| H A D | xenbus_client.c | 568 bool *leaked) in __xenbus_map_ring() argument
607 *leaked = false; in __xenbus_map_ring()
610 *leaked = true; in __xenbus_map_ring()
683 bool leaked = false; in xenbus_map_ring_hvm() local
695 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() local
779 &leaked); in xenbus_map_ring_pv()
796 if (!leaked) in xenbus_map_ring_pv()
[all …]
|
| /linux/Documentation/staging/ |
| H A D | speculation.rst | 48 result in sensitive information being leaked. Consider the following
75 prevent information from being leaked via side-channels.
|
| /linux/drivers/xen/ |
| H A D | grant-table.c | 558 uint64_t leaked, deferred; in gnttab_add_deferred() local
582 leaked = atomic64_read(&leaked_count); in gnttab_add_deferred()
584 ref, page ? page_to_pfn(page) : -1, deferred, leaked); in gnttab_add_deferred()
587 leaked = atomic64_inc_return(&leaked_count); in gnttab_add_deferred()
589 ref, page ? page_to_pfn(page) : -1, deferred, leaked); in gnttab_add_deferred()
|
| /linux/drivers/soc/fsl/qbman/ |
| H A D | qman.c | 1830 int leaked; in qman_destroy_fq() local
1845 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()
|
| /linux/tools/testing/selftests/tc-testing/ |
| H A D | README | 195 and the other is a test whether the command leaked memory or not.
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | spectre.rst | 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
|
| H A D | tsx_async_abort.rst | 76 be leaked. Only the victim is responsible for bringing data to the CPU. As
|
| /linux/Documentation/arch/x86/ |
| H A D | mds.rst | 111 itself are not required because the necessary gadgets to expose the leaked
|
| H A D | sgx.rst | 236 "EREMOVE returned ... and an EPC page was leaked. SGX may become unusable..."
|
| /linux/security/ |
| H A D | Kconfig.hardening | 200 leaked beyond the function boundary. This means that register
|
| /linux/Documentation/security/tpm/ |
| H A D | tpm-security.rst | 109 during boot may have been leaked).
|
| /linux/Documentation/scsi/ |
| H A D | ChangeLog.megaraid_sas | 24 3. Return leaked MPT frames to MPT command pool.
|
| /linux/Documentation/RCU/ |
| H A D | checklist.rst | 506 combine with KASAN to check for pointers leaked out
|
| /linux/Documentation/filesystems/ |
| H A D | fscrypt.rst | 1352 kernel memory is leaked. This is done without limiting the number of
|