Searched refs:poisoned (Results 1 – 10 of 10) sorted by relevance
28 READ_AFTER_FREE call trace:|Memory correctly poisoned30 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
386 The poison file specifies whether objects should be poisoned
596 list consists of addresses that are poisoned, or would result
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()
20 一个页面"poisoned"，杀死与之相关的进程，并避免在未来使用它。
205 After entering the kernel, the kernel could use the poisoned branch214 The kernel can protect itself against consuming poisoned branch265 a deeper call stack. Any poisoned entries in the return stack buffer289 for indirect branches to bypass the poisoned branch target buffer,311 stack buffer. Such poisoned entries could be used to influence537 This protects them from consuming poisoned entries in the branch572 poisoned entries in branch target buffer left by rogue guests. It also574 stack buffer underflow so poisoned branch target buffer could be used,575 or attacker guests leaving poisoned entries in the return stack buffer.
53 poisoned RSB entries using an RSB filling sequence138 On AMD, poisoned RSB entries can also be created by the AMD RETBleed162 to using a poisoned BTB entry.
1431 unsigned int poisoned:1; member
235 bool poisoned = bpf_map_key_poisoned(aux); in bpf_map_key_store() local238 (poisoned ? BPF_MAP_KEY_POISON : 0ULL); in bpf_map_key_store()