Message-Id: <20090620031608.624240019@intel.com>
Date:	Sat, 20 Jun 2009 11:16:08 +0800
From:	Wu Fengguang <fengguang.wu@...el.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	"Wu, Fengguang" <fengguang.wu@...el.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Nick Piggin <npiggin@...e.de>,
	Hugh Dickins <hugh.dickins@...cali.co.uk>,
	Andi Kleen <andi@...stfloor.org>,
	"riel@...hat.com" <riel@...hat.com>,
	"chris.mason@...cle.com" <chris.mason@...cle.com>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>
Subject: [PATCH 00/15] HWPOISON: Intro (v6)

Hi Andrew,

Now we default to the less intrusive late kill, together with a per process
tunable option to early kill as proposed by Nick and Hugh. It also invalidates
the mapping page in a safe manner and stops messing with dirty/writeback pages
for now.

Comments are welcome!

changes since v5:
- interface: remove the global vm.memory_failure_early_kill;
  introduce prctl(PR_MEMORY_FAILURE_EARLY_KILL)
- early kill: check for page_mapped_in_vma() on anon pages
- early kill: test and use page->mapping instead of page_mapping()
- be safe: introduce invalidate_inode_page() and don't remove dirty/writeback
  pages from page cache
- account all poisoned pages in mce_bad_pages
- taint kernel on hwpoison pages in bad_page()
- comment updates
- don't do uevent for now
- don't mess with dirty/writeback pages for now

changes since v4:
- new feature: uevent report (and collect various states for that)
- early kill cleanups
- remove unnecessary code in __do_fault()
- fix compile error when feature not enabled
- fix kernel oops when invalid pfn is feed to corrupt-pfn
- make tasklist_lock/anon_vma locking order straight
- use the safer invalidate page for possible metadata pages

  [PATCH 01/15] HWPOISON: Add page flag for poisoned pages
  [PATCH 02/15] HWPOISON: Export some rmap vma locking to outside world
  [PATCH 03/15] HWPOISON: Add support for poison swap entries v2
  [PATCH 04/15] HWPOISON: Add new SIGBUS error codes for hardware poison signals
  [PATCH 05/15] HWPOISON: Add basic support for poisoned pages in fault handler v3
  [PATCH 06/15] HWPOISON: x86: Add VM_FAULT_HWPOISON handling to x86 page fault handler v2
  [PATCH 07/15] HWPOISON: define VM_FAULT_HWPOISON to 0 when feature is disabled
  [PATCH 08/15] HWPOISON: Use bitmask/action code for try_to_unmap behaviour
  [PATCH 09/15] HWPOISON: Handle hardware poisoned pages in try_to_unmap
  [PATCH 10/15] HWPOISON: check and isolate corrupted free pages v3
  [PATCH 11/15] HWPOISON: The high level memory error handler in the VM v8
  [PATCH 12/15] HWPOISON: per process early kill option prctl(PR_MEMORY_FAILURE_EARLY_KILL)
  [PATCH 13/15] HWPOISON: Add madvise() based injector for hardware poisoned pages v3
  [PATCH 14/15] HWPOISON: Add simple debugfs interface to inject hwpoison on arbitary PFNs
  [PATCH 15/15] HWPOISON: FOR TESTING: Enable memory failure code unconditionally

---
Upcoming Intel CPUs have support for recovering from some memory errors
(``MCA recovery''). This requires the OS to declare a page "poisoned",
kill the processes associated with it and avoid using it in the future.

This patchkit implements the necessary infrastructure in the VM.

To quote the overview comment:

 * High level machine check handler. Handles pages reported by the
 * hardware as being corrupted usually due to a 2bit ECC memory or cache
 * failure.
 *
 * This focusses on pages detected as corrupted in the background.
 * When the current CPU tries to consume corruption the currently
 * running process can just be killed directly instead. This implies
 * that if the error cannot be handled for some reason it's safe to
 * just ignore it because no corruption has been consumed yet. Instead
 * when that happens another machine check will happen.
 *
 * Handles page cache pages in various states. The tricky part
 * here is that we can access any page asynchronous to other VM
 * users, because memory failures could happen anytime and anywhere,
 * possibly violating some of their assumptions. This is why this code
 * has to be extremely careful. Generally it tries to use normal locking
 * rules, as in get the standard locks, even if that means the
 * error handling takes potentially a long time.
 *
 * Some of the operations here are somewhat inefficient and have non
 * linear algorithmic complexity, because the data structures have not
 * been optimized for this case. This is in particular the case
 * for the mapping from a vma to a process. Since this case is expected
 * to be rare we hope we can get away with this.

The code consists of a the high level handler in mm/memory-failure.c,
a new page poison bit and various checks in the VM to handle poisoned
pages.

The main target right now is KVM guests, but it works for all kinds
of applications.

For the KVM use there was need for a new signal type so that
KVM can inject the machine check into the guest with the proper
address. This in theory allows other applications to handle
memory failures too. The expection is that near all applications
won't do that, but some very specialized ones might.

This is not fully complete yet, in particular there are still ways
to access poison through various ways (crash dump, /proc/kcore etc.)
that need to be plugged too.
Also undoubtedly the high level handler still has bugs and cases
it cannot recover from. For example nonlinear mappings deadlock right now
and a few other cases lose references. Huge pages are not supported
yet. Any additional testing, reviewing etc. welcome.

The patch series requires the earlier x86 MCE feature series for the x86
specific action optional part. The code can be tested without the x86 specific
part using the injector, this only requires to enable the Kconfig entry
manually in some Kconfig file (by default it is implicitely enabled
by the architecture)

v2: Lots of smaller changes in the series based on review feedback.
Rename Poison to HWPoison after akpm's request.
A new pfn based injector based on feedback.
A lot of improvements mostly from Fengguang Wu
See comments in the individual patches.
v3: Various updates, see changelogs in individual patches.
v4: Various updates, see changelogs in individual patches.

Thanks,
Fengguang
-- 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists