lkml.org 
[lkml]   [2009]   [Sep]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH] [6/21] HWPOISON: Add various poison checks in mm/memory.c v2
    Date

    Bail out early when hardware poisoned pages are found in page fault handling.
    Since they are poisoned they should not be mapped freshly into processes,
    because that would cause another (potentially deadly) machine check

    This is generally handled in the same way as OOM, just a different
    error code is returned to the architecture code.

    v2: Do a page unlock if needed (Fengguang Wu)

    Signed-off-by: Andi Kleen <ak@linux.intel.com>

    ---
    mm/memory.c | 6 ++++++
    1 file changed, 6 insertions(+)

    Index: linux/mm/memory.c
    ===================================================================
    --- linux.orig/mm/memory.c
    +++ linux/mm/memory.c
    @@ -2711,6 +2711,12 @@ static int __do_fault(struct mm_struct *
    if (unlikely(ret & (VM_FAULT_ERROR | VM_FAULT_NOPAGE)))
    return ret;

    + if (unlikely(PageHWPoison(vmf.page))) {
    + if (ret & VM_FAULT_LOCKED)
    + unlock_page(vmf.page);
    + return VM_FAULT_HWPOISON;
    + }
    +
    /*
    * For consistency in subsequent calls, make the faulted page always
    * locked.

    \
     
     \ /
      Last update: 2009-09-11 20:51    [W:0.046 / U:0.272 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site