Searched refs:poisoned (Results 1 – 11 of 11) sorted by relevance
23 READ_AFTER_FREE call trace:|Memory correctly poisoned25 READ_BUDDY_AFTER_FREE call trace:|Memory correctly poisoned
17 The page must be still accessible, not poisoned. The35 to access this page assuming it's poisoned by the
383 The poison file specifies whether objects should be poisoned
136 if (unlikely(anchor->poisoned)) in usb_anchor_urb()868 anchor->poisoned = 1; in usb_poison_anchored_urbs()904 anchor->poisoned = 0; in usb_unpoison_anchored_urbs()
20 一个页面"poisoned"，杀死与之相关的进程，并避免在未来使用它。
206 After entering the kernel, the kernel could use the poisoned branch215 The kernel can protect itself against consuming poisoned branch266 a deeper call stack. Any poisoned entries in the return stack buffer290 for indirect branches to bypass the poisoned branch target buffer,312 stack buffer. Such poisoned entries could be used to influence506 This protects them from consuming poisoned entries in the branch538 poisoned entries in branch target buffer left by rogue guests. It also540 stack buffer underflow so poisoned branch target buffer could be used,541 or attacker guests leaving poisoned entries in the return stack buffer.
11 (``MCA recovery``). This requires the OS to declare a page "poisoned",44 a new page poison bit and various checks in the VM to handle poisoned
134 When a new variable is allocated on the stack, it is poisoned by default by137 ``__GFP_ZERO`` is also poisoned.174 If a poisoned value is written into memory, its origin is written to the310 ``__msan_warning()`` in the case that value is poisoned::
1364 unsigned int poisoned:1; member
508 2. ``ap->active_tag`` and ``qc->tag`` are poisoned.
230 bool poisoned = bpf_map_key_poisoned(aux); in bpf_map_key_store() local233 (poisoned ? BPF_MAP_KEY_POISON : 0ULL); in bpf_map_key_store()
