Searched refs:poisoned (Results 1 – 9 of 9) sorted by relevance
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
135 if (unlikely(anchor->poisoned)) in usb_anchor_urb()857 anchor->poisoned = 1; in usb_poison_anchored_urbs()893 anchor->poisoned = 0; in usb_unpoison_anchored_urbs()
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 branch539 poisoned entries in branch target buffer left by rogue guests. It also541 stack buffer underflow so poisoned branch target buffer could be used,542 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
1372 unsigned int poisoned:1; member
519 2. ``ap->active_tag`` and ``qc->tag`` are poisoned.
225 bool poisoned = bpf_map_key_poisoned(aux); in bpf_map_key_store() local228 (poisoned ? BPF_MAP_KEY_POISON : 0ULL); in bpf_map_key_store()
15412 - * not use it at all. Let's provide some poisoned pointer to catch