Searched refs:poisoned (Results 1 – 6 of 6) 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
135 if (unlikely(anchor->poisoned)) in usb_anchor_urb()821 anchor->poisoned = 1; in usb_poison_anchored_urbs()853 anchor->poisoned = 0; in usb_unpoison_anchored_urbs()
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
1349 unsigned int poisoned:1; member
519 2. ``ap->active_tag`` and ``qc->tag`` are poisoned.
