Searched refs:leaked (Results 1 – 16 of 16) sorted by relevance
| /kernel/linux/linux-5.10/drivers/xen/xenbus/ |
| D | xenbus_client.c | 506 bool *leaked) in __xenbus_map_ring() argument
546 *leaked = false; in __xenbus_map_ring()
549 *leaked = true; in __xenbus_map_ring()
622 bool leaked = false; in xenbus_map_ring_hvm() local
634 info, GNTMAP_host_map, &leaked); in xenbus_map_ring_hvm()
659 if (!leaked) in xenbus_map_ring_hvm()
665 if (!leaked) in xenbus_map_ring_hvm()
706 bool leaked = false; in xenbus_map_ring_pv() local
717 &leaked); in xenbus_map_ring_pv()
734 if (!leaked) in xenbus_map_ring_pv()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/staging/ |
| D | speculation.rst | 48 result in sensitive information being leaked. Consider the following
76 prevent information from being leaked via side-channels.
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | balance.rst | 71 are not leaked (for example, in situations where a HIGHMEM page is in
|
| D | hugetlbfs_reserv.rst | 551 so that a reservation will not be leaked when the huge page is freed.
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 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
|
| D | tsx_async_abort.rst | 76 be leaked. Only the victim is responsible for bringing data to the CPU. As
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | mds.rst | 108 itself are not required because the necessary gadgets to expose the leaked
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | dma-buf.rst | 71 access to buffers, via the leaked fd, to which it should otherwise
|
| /kernel/linux/linux-5.10/tools/testing/selftests/tc-testing/ |
| D | README | 240 and the other is a test whether the command leaked memory or not.
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | maintainer-pgp-guide.rst | 206 disk. This way, even if your ``.gnupg`` directory is leaked or stolen in
326 think. They can be leaked or stolen via many different means:
407 Even though the master key is now safe from being leaked or stolen, the
|
| /kernel/linux/linux-5.10/Documentation/ia64/ |
| D | fsys.rst | 38 security-sensitive kernel-level state is leaked back to
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | ChangeLog.megaraid_sas | 24 3. Return leaked MPT frames to MPT command pool.
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | filter.rst | 1258 reference is not leaked, it is imperative to NULL-check the reference and in
|
| /kernel/linux/patches/linux-5.10/imx8mm_patch/patches/drivers/ |
| D | 0036_linux_drivers_staging.patch | 18311 + so the pool must be leaked */
18381 + " CGR will be leaked\n",
19913 + " recover portal, portal will be leaked\n");
|
| D | 0038_linux_drivers_mxc.patch | 74224 + gctSIZE_T leaked = 0;
74247 + leaked += node->bytes;
74263 + /* Return the number of leaked bytes. */
74264 + return leaked;
74518 + gctSIZE_T leaked = 0;
74529 + /* Check for leaked memory. */
74530 + leaked += _DumpHeap(heap);
74545 + gcmkFOOTER_ARG("leaked=%lu", leaked);
|
| /kernel/linux/patches/linux-5.10/imx8mm_patch/patches/ |
| D | 0005_linux_include.patch | 6286 + * always succeeds, but returns non-zero if there were "leaked" FQID
|