HWPOISON: limit hwpoison injector to known page types
authorWu Fengguang <fengguang.wu@intel.com>
Wed, 16 Dec 2009 11:19:59 +0000 (12:19 +0100)
committerAndi Kleen <ak@linux.intel.com>
Wed, 16 Dec 2009 11:19:59 +0000 (12:19 +0100)
commit31d3d3484f9bd263925ecaa341500ac2df3a5d9b
tree38f331f27f3b4bc537303fc90490b88d53e43710
parent7c116f2b0dbac4a1dd051c7a5e8cef37701cafd4
HWPOISON: limit hwpoison injector to known page types

__memory_failure()'s workflow is

set PG_hwpoison
//...
unset PG_hwpoison if didn't pass hwpoison filter

That could kill unrelated process if it happens to page fault on the
page with the (temporary) PG_hwpoison. The race should be big enough to
appear in stress tests.

Fix it by grabbing the page and checking filter at inject time.  This
also avoids the very noisy "Injecting memory failure..." messages.

- we don't touch madvise() based injection, because the filters are
  generally not necessary for it.
- if we want to apply the filters to h/w aided injection, we'd better to
  rearrange the logic in __memory_failure() instead of this patch.

AK: fix documentation, use drain all, cleanups

CC: Haicheng Li <haicheng.li@intel.com>
Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Documentation/vm/hwpoison.txt
mm/hwpoison-inject.c
mm/internal.h