Searched refs:poisoned (Results 1 – 15 of 15) sorted by relevance
| /Linux-v6.6/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-v6.6/tools/testing/selftests/lkdtm/ |
| D | tests.txt | 23 READ_AFTER_FREE call trace:|Memory correctly poisoned
25 READ_BUDDY_AFTER_FREE call trace:|Memory correctly poisoned
|
| /Linux-v6.6/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-bus-cxl | 486 list consists of addresses that are poisoned, or would result
|
| D | sysfs-kernel-slab | 383 The poison file specifies whether objects should be poisoned
|
| /Linux-v6.6/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-v6.6/Documentation/translations/zh_CN/mm/ |
| D | hwpoison.rst | 20 一个页面"poisoned"，杀死与之相关的进程，并避免在未来使用它。
|
| /Linux-v6.6/Documentation/admin-guide/hw-vuln/ |
| D | spectre.rst | 206 After entering the kernel, the kernel could use the poisoned branch
215 The kernel can protect itself against consuming poisoned branch
266 a deeper call stack. Any poisoned entries in the return stack buffer
290 for indirect branches to bypass the poisoned branch target buffer,
312 stack buffer. Such poisoned entries could be used to influence
517 This protects them from consuming poisoned entries in the branch
552 poisoned entries in branch target buffer left by rogue guests. It also
554 stack buffer underflow so poisoned branch target buffer could be used,
555 or attacker guests leaving poisoned entries in the return stack buffer.
|
| D | srso.rst | 146 poisoned BTB entry and using that safe one for all function returns.
|
| /Linux-v6.6/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-v6.6/Documentation/dev-tools/ |
| D | kmsan.rst | 134 When a new variable is allocated on the stack, it is poisoned by default by
137 ``__GFP_ZERO`` is also poisoned.
174 If a poisoned value is written into memory, its origin is written to the
310 ``__msan_warning()`` in the case that value is poisoned::
|
| /Linux-v6.6/include/linux/ |
| D | usb.h | 1402 unsigned int poisoned:1; member
|
| /Linux-v6.6/Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 259 still poisoned, even though it's on a new physical host which ostensibly
|
| /Linux-v6.6/Documentation/driver-api/ |
| D | libata.rst | 483 2. ``ap->active_tag`` and ``qc->tag`` are poisoned.
|
| /Linux-v6.6/kernel/bpf/ |
| D | verifier.c | 240 bool poisoned = bpf_map_key_poisoned(aux); in bpf_map_key_store() local
243 (poisoned ? BPF_MAP_KEY_POISON : 0ULL); in bpf_map_key_store()
|
