[PATCH 1/3] Avoid unmapping THP when it is failed to be split.
From: Jin Dongming
Date: Tue Jan 25 2011 - 00:42:42 EST
If the THP is failed to be split,
1. The processes using the poisoned page could not be collected.
(Because page_mapped_in_vma() in collect_procs_anon() always
returns NULL.)
2. The poisoned page could not be unmapped.
(If CONFIG_DEBUG_VM is "y", VM_BUG_ON(PageTransHuge(page))
in try_to_unmap() will be called, and system panic will be
caused.)
3. The processes using the poisoned page could not be killed, too.
(Because no process is collected in 1.)
So if splitting THP is failed, it is better to stop unmapping
rather than causing panic. System might servive if the page is freed
later.
Signed-off-by: Jin Dongming <jin.dongming@xxxxxxxxxxxxxxxxxx>
Reviewed-by: Hidetoshi Seto <seto.hidetoshi@xxxxxxxxxxxxxx>
---
mm/memory-failure.c | 13 +++++++++++--
1 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/mm/memory-failure.c b/mm/memory-failure.c
index 548fbd7..55f7d07 100644
--- a/mm/memory-failure.c
+++ b/mm/memory-failure.c
@@ -386,8 +386,6 @@ static void collect_procs_anon(struct page *page, struct list_head *to_kill,
struct task_struct *tsk;
struct anon_vma *av;
- if (!PageHuge(page) && unlikely(split_huge_page(page)))
- return;
read_lock(&tasklist_lock);
av = page_lock_anon_vma(page);
if (av == NULL) /* Not actually mapped anymore */
@@ -896,6 +894,17 @@ static int hwpoison_user_mappings(struct page *p, unsigned long pfn,
}
}
+ if (!PageHuge(hpage) && PageAnon(hpage) &&
+ unlikely(split_huge_page(hpage))) {
+ /*
+ * FIXME: if splitting THP is failed, it is better to stop
+ * the following operation rather than causing panic
+ * by unmapping. System might survive if the page is freed later.
+ */
+ printk(KERN_INFO "MCE %#lx: failed to split THP\n", pfn);
+ return SWAP_FAIL;
+ }
+
/*
* First collect all the processes that have the page
* mapped in dirty form. This has to be done before try_to_unmap,
--
1.7.2.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/