Searched refs:poisoned (Results 1 – 16 of 16) sorted by relevance
| /linux-6.12.1/Documentation/ABI/stable/ |
| D | sysfs-devices-node | 190 The total number of raw poisoned pages (pages containing
197 Of the raw poisoned pages on a NUMA node, how many pages are
206 Of the raw poisoned pages on a NUMA node, how many pages are
214 Of the raw poisoned pages on a NUMA node, how many pages are
215 delayed by memory error recovery attempt. Delayed poisoned
222 Of the raw poisoned pages on a NUMA node, how many pages are
|
| /linux-6.12.1/tools/testing/selftests/lkdtm/ |
| D | tests.txt | 24 READ_AFTER_FREE call trace:|Memory correctly poisoned
26 READ_BUDDY_AFTER_FREE call trace:|Memory correctly poisoned
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-memory-page-offline | 17 The page must be still accessible, not poisoned. The
35 to access this page assuming it's poisoned by the
|
| D | sysfs-kernel-slab | 383 The poison file specifies whether objects should be poisoned
|
| D | sysfs-bus-cxl | 550 list consists of addresses that are poisoned, or would result
|
| /linux-6.12.1/drivers/usb/core/ |
| D | urb.c | 136 if (unlikely(anchor->poisoned)) in usb_anchor_urb()
853 anchor->poisoned = 1; in usb_poison_anchored_urbs()
889 anchor->poisoned = 0; in usb_unpoison_anchored_urbs()
|
| /linux-6.12.1/Documentation/translations/zh_CN/mm/ |
| D | hwpoison.rst | 20 一个页面"poisoned"，杀死与之相关的进程，并避免在未来使用它。
|
| /linux-6.12.1/Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 205 After entering the kernel, the kernel could use the poisoned branch
214 The kernel can protect itself against consuming poisoned branch
265 a deeper call stack. Any poisoned entries in the return stack buffer
289 for indirect branches to bypass the poisoned branch target buffer,
311 stack buffer. Such poisoned entries could be used to influence
537 This protects them from consuming poisoned entries in the branch
572 poisoned entries in branch target buffer left by rogue guests. It also
574 stack buffer underflow so poisoned branch target buffer could be used,
575 or attacker guests leaving poisoned entries in the return stack buffer.
|
| D | srso.rst | 156 poisoned BTB entry and using that safe one for all function returns.
|
| /linux-6.12.1/Documentation/dev-tools/ |
| D | kmsan.rst | 141 When a new variable is allocated on the stack, it is poisoned by default by
144 ``__GFP_ZERO`` is also poisoned.
181 If a poisoned value is written into memory, its origin is written to the
317 ``__msan_warning()`` in the case that value is poisoned::
|
| /linux-6.12.1/Documentation/mm/ |
| D | hwpoison.rst | 9 (``MCA recovery``). This requires the OS to declare a page "poisoned",
42 a new page poison bit and various checks in the VM to handle poisoned
|
| /linux-6.12.1/include/linux/ |
| D | usb.h | 1403 unsigned int poisoned:1; member
|
| /linux-6.12.1/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 297 still poisoned, even though it's on a new physical host which ostensibly
|
| /linux-6.12.1/Documentation/driver-api/ |
| D | libata.rst | 483 2. ``ap->active_tag`` and ``qc->tag`` are poisoned.
|
| /linux-6.12.1/arch/x86/ |
| D | Kconfig | 2641 where the branch history buffer is poisoned to speculatively steer
|
| /linux-6.12.1/kernel/bpf/ |
| D | verifier.c | 244 bool poisoned = bpf_map_key_poisoned(aux); in bpf_map_key_store() local
247 (poisoned ? BPF_MAP_KEY_POISON : 0ULL); in bpf_map_key_store()
|