Home
last modified time | relevance | path

Searched refs:leaked (Results 1 – 25 of 38) sorted by relevance

12

/openbmc/linux/drivers/xen/xenbus/
H A Dxenbus_client.c551 bool *leaked) in __xenbus_map_ring() argument
590 *leaked = false; in __xenbus_map_ring()
593 *leaked = true; in __xenbus_map_ring()
665 bool leaked = false; in xenbus_map_ring_hvm() local
677 info, GNTMAP_host_map, &leaked); in xenbus_map_ring_hvm()
702 if (!leaked) in xenbus_map_ring_hvm()
708 if (!leaked) in xenbus_map_ring_hvm()
749 bool leaked = false; in xenbus_map_ring_pv() local
760 &leaked); in xenbus_map_ring_pv()
777 if (!leaked) in xenbus_map_ring_pv()
[all …]
/openbmc/qemu/tests/qemu-iotests/
H A D108.out15 0 leaked clusters
39 0 leaked clusters
56 0 leaked clusters
73 0 leaked clusters
89 0 leaked clusters
105 0 leaked clusters
123 0 leaked clusters
145 0 leaked clusters
186 0 leaked clusters
H A D217.out21 4 leaked clusters were found on the image.
37 4 leaked clusters
H A D060.out49 0 leaked clusters
72 1 leaked clusters were found on the image.
85 1 leaked clusters
200 0 leaked clusters
222 0 leaked clusters
242 0 leaked clusters
264 0 leaked clusters
279 0 leaked clusters
308 1 leaked clusters
327 0 leaked clusters
[all …]
H A D112.out38 1 leaked clusters were found on the image.
50 1 leaked clusters were found on the image.
82 2 leaked clusters were found on the image.
137 0 leaked clusters
H A D261.out59 0 leaked clusters
196 0 leaked clusters
223 4 leaked clusters
252 2 leaked clusters
354 42 leaked clusters
H A D272.out8 2044 leaked clusters were found on the image.
H A D070.out13 0 leaked clusters
H A D080.out82 3 leaked clusters were found on the image.
105 3 leaked clusters were found on the image.
H A D214.out26 0 leaked clusters
H A D220.out52 8388589 leaked clusters were found on the image.
H A D039.out34 0 leaked clusters
/openbmc/qemu/tests/qemu-iotests/tests/
H A Dparallels-checks.out22 Repairing space leaked at the end of the image 1048576
25 1 leaked clusters
53 0 leaked clusters
124 0 leaked clusters
/openbmc/linux/Documentation/staging/
H A Dspeculation.rst48 result in sensitive information being leaked. Consider the following
76 prevent information from being leaked via side-channels.
/openbmc/linux/drivers/xen/
H A Dgrant-table.c559 uint64_t leaked, deferred; in gnttab_add_deferred() local
583 leaked = atomic64_read(&leaked_count); in gnttab_add_deferred()
585 ref, page ? page_to_pfn(page) : -1, deferred, leaked); in gnttab_add_deferred()
588 leaked = atomic64_inc_return(&leaked_count); in gnttab_add_deferred()
590 ref, page ? page_to_pfn(page) : -1, deferred, leaked); in gnttab_add_deferred()
/openbmc/openbmc/poky/meta/recipes-extended/lsof/files/
H A Dremove-host-information.patch8 ensure that no host information is leaked into the binary.
/openbmc/linux/Documentation/mm/
H A Dbalance.rst69 are not leaked (for example, in situations where a HIGHMEM page is in
/openbmc/qemu/docs/interop/
H A Dqed_spec.txt134 …luster referenced more than once by L1 or L2 tables. A cluster has been leaked if it has no refer…
/openbmc/linux/rust/alloc/
H A Dboxed.rs1108 let (leaked, alloc) = Box::into_unique(b); in into_raw_with_allocator()
1109 (leaked.as_ptr(), alloc) in into_raw_with_allocator()
/openbmc/linux/Documentation/admin-guide/hw-vuln/
H A Dspectre.rst164 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 Dtsx_async_abort.rst76 be leaked. Only the victim is responsible for bringing data to the CPU. As
/openbmc/openbmc/poky/documentation/dev-manual/
H A Dsecurity-subjects.rst80 the exploit is not leaked and exploited before a response/fix has been generated.
/openbmc/linux/Documentation/arch/x86/
H A Dmds.rst111 itself are not required because the necessary gadgets to expose the leaked
/openbmc/linux/tools/testing/selftests/tc-testing/
H A DREADME240 and the other is a test whether the command leaked memory or not.
/openbmc/linux/Documentation/process/
H A Dmaintainer-pgp-guide.rst184 disk. This way, even if your ``.gnupg`` directory is leaked or stolen in
286 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

12