[PATCH] [8/16] POISON: Add various poison checks in mm/memory.c

Andi Kleen
2009-04-07T15:21:59Z

Bail out early when poisoned pages are found in page fault handling.
Since they are poisoned they should not be mapped freshly
into processes.

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

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

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

Index: linux/mm/memory.c
===================================================================
--- linux.orig/mm/memory.c 2009-04-07 16:39:39.000000000 +0200
+++ linux/mm/memory.c 2009-04-07 16:39:39.000000000 +0200
@@ -2560,6 +2560,10 @@
goto oom;
__SetPageUptodate(page);

+ /* Kludge for now until we take poisoned pages out of the free lists */
+ if (unlikely(PagePoison(page)))
+ return VM_FAULT_POISON;
+
if (mem_cgroup_newpage_charge(page, mm, GFP_KERNEL))
goto oom_free_page;

@@ -2625,6 +2629,9 @@
if (unlikely(ret & (VM_FAULT_ERROR | VM_FAULT_NOPAGE)))
return ret;

+ if (unlikely(PagePoison(vmf.page)))
+ return VM_FAULT_POISON;
+
/*
* For consistency in subsequent calls, make the faulted page always
* locked.