Searched refs:poisoned (Results 1 – 7 of 7) sorted by relevance
17 The page must be still accessible, not poisoned. The35 to access this page assuming it's poisoned by the
381 The poison file specifies whether objects should be poisoned
134 if (unlikely(anchor->poisoned)) in usb_anchor_urb()820 anchor->poisoned = 1; in usb_poison_anchored_urbs()852 anchor->poisoned = 0; in usb_unpoison_anchored_urbs()
193 After entering the kernel, the kernel could use the poisoned branch202 The kernel can protect itself against consuming poisoned branch253 a deeper call stack. Any poisoned entries in the return stack buffer277 for indirect branches to bypass the poisoned branch target buffer,299 stack buffer. Such poisoned entries could be used to influence483 This protects them from consuming poisoned entries in the branch516 poisoned entries in branch target buffer left by rogue guests. It also518 stack buffer underflow so poisoned branch target buffer could be used,519 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
1354 unsigned int poisoned:1; member
519 2. ``ap->active_tag`` and ``qc->tag`` are poisoned.
