From: Nick Piggin <npiggin@suse.de>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Mel Gorman <mel@csn.ul.ie>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Hugh Dickins <hugh.dickins@tiscali.co.uk>,
Andi Kleen <andi@firstfloor.org>,
"riel@redhat.com" <riel@redhat.com>,
"chris.mason@oracle.com" <chris.mason@oracle.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH 00/22] HWPOISON: Intro (v5)
Date: Mon, 15 Jun 2009 08:44:47 +0200 [thread overview]
Message-ID: <20090615064447.GA18390@wotan.suse.de> (raw)
In-Reply-To: <20090615042753.GA20788@localhost>
On Mon, Jun 15, 2009 at 12:27:53PM +0800, Wu Fengguang wrote:
> On Mon, Jun 15, 2009 at 11:18:18AM +0800, Balbir Singh wrote:
> > Wu Fengguang wrote:
> > > Hi all,
> > >
> > > Comments are warmly welcome on the newly introduced uevent code :)
> > >
> > > I hope we can reach consensus in this round and then be able to post
> > > a final version for .31 inclusion.
> >
> > Isn't that too aggressive? .31 is already in the merge window.
>
> Yes, a bit aggressive. This is a new feature that involves complex logics.
> However it is basically a no-op when there are no memory errors,
> and when memory corruption does occur, it's better to (possibly) panic
> in this code than to panic unconditionally in the absence of this
> feature (as said by Rik).
>
> So IMHO it's OK for .31 as long as we agree on the user interfaces,
> ie. /proc/sys/vm/memory_failure_early_kill and the hwpoison uevent.
>
> It comes a long way through numerous reviews, and I believe all the
> important issues and concerns have been addressed. Nick, Rik, Hugh,
> Ingo, ... what are your opinions? Is the uevent good enough to meet
> your request to "die hard" or "die gracefully" or whatever on memory
> failure events?
Uevent? As in, send a message to userspace? I don't think this
would be ideal for a fail-stop/failover situation.
I can't see a good reason to rush to merge it.
IMO the userspace-visible changes have maybe not been considered
too thoroughly, which is what I'd be most worried about. I probably
missed seeing documentation of exact semantics and situations
where admins should tune things one way or the other.
Did we verify with filesystem maintainers (eg. btrfs) that the
!ISREG test will be enough to prevent oopses?
I hope it is going to be merged with an easy-to-use fault injector,
because that is the only way Joe kernel developer is ever going to
test it.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-06-15 6:43 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 2:45 [PATCH 00/22] HWPOISON: Intro (v5) Wu Fengguang
2009-06-15 2:45 ` [PATCH 01/22] HWPOISON: Add page flag for poisoned pages Wu Fengguang
2009-06-15 2:45 ` [PATCH 02/22] HWPOISON: Export some rmap vma locking to outside world Wu Fengguang
2009-06-15 2:45 ` [PATCH 03/22] HWPOISON: Add support for poison swap entries v2 Wu Fengguang
2009-06-15 2:45 ` [PATCH 04/22] HWPOISON: Add new SIGBUS error codes for hardware poison signals Wu Fengguang
2009-06-15 2:45 ` [PATCH 05/22] HWPOISON: Add basic support for poisoned pages in fault handler v3 Wu Fengguang
2009-06-15 2:45 ` [PATCH 06/22] HWPOISON: x86: Add VM_FAULT_HWPOISON handling to x86 page fault handler v2 Wu Fengguang
2009-06-15 2:45 ` [PATCH 07/22] HWPOISON: define VM_FAULT_HWPOISON to 0 when feature is disabled Wu Fengguang
2009-06-15 2:45 ` [PATCH 08/22] HWPOISON: Use bitmask/action code for try_to_unmap behaviour Wu Fengguang
2009-06-15 2:45 ` [PATCH 09/22] HWPOISON: Handle hardware poisoned pages in try_to_unmap Wu Fengguang
2009-06-15 13:09 ` Minchan Kim
2009-06-15 15:26 ` Wu Fengguang
2009-06-16 0:03 ` Minchan Kim
2009-06-16 13:49 ` Wu Fengguang
2009-06-17 0:28 ` Minchan Kim
2009-06-17 7:23 ` Wu Fengguang
2009-06-17 13:27 ` Minchan Kim
2009-06-17 13:37 ` Wu Fengguang
2009-06-17 13:43 ` Minchan Kim
2009-06-17 14:03 ` Wu Fengguang
2009-06-17 14:08 ` Minchan Kim
2009-06-17 14:12 ` Wu Fengguang
[not found] ` <28c262360906170644w65c08a8y2d2805fb08045804@mail.gmail.com>
[not found] ` <20090617135543.GA8079@localhost>
[not found] ` <28c262360906170703h3363b68dp74471358f647921e@mail.gmail.com>
2009-06-18 12:14 ` Wu Fengguang
2009-06-18 13:31 ` Minchan Kim
2009-06-19 1:58 ` Wu Fengguang
2009-06-15 2:45 ` [PATCH 10/22] HWPOISON: check and isolate corrupted free pages v2 Wu Fengguang
2009-06-15 9:41 ` KAMEZAWA Hiroyuki
2009-06-15 10:16 ` Wu Fengguang
2009-06-15 23:52 ` KAMEZAWA Hiroyuki
2009-06-16 0:34 ` Wu Fengguang
2009-06-16 11:29 ` Hugh Dickins
2009-06-16 11:40 ` Wu Fengguang
2009-06-15 2:45 ` [PATCH 11/22] HWPOISON: Refactor truncate to allow direct truncating of page v3 Wu Fengguang
2009-06-15 2:45 ` [PATCH 12/22] HWPOISON: The high level memory error handler in the VM v7 Wu Fengguang
2009-06-15 2:45 ` [PATCH 13/22] HWPOISON: Add madvise() based injector for hardware poisoned pages v3 Wu Fengguang
2009-06-15 2:45 ` [PATCH 14/22] HWPOISON: Add simple debugfs interface to inject hwpoison on arbitary PFNs Wu Fengguang
2009-06-15 2:45 ` [PATCH 15/22] HWPOISON: early kill cleanups and fixes Wu Fengguang
2009-06-15 2:45 ` [PATCH 16/22] mm: move page flag numbers for user space to page-flags.h Wu Fengguang
2009-06-15 2:45 ` [PATCH 17/22] HWPOISON: introduce struct hwpoison_control Wu Fengguang
2009-06-15 2:45 ` [PATCH 18/22] HWPOISON: use compound head page Wu Fengguang
2009-06-15 2:45 ` [PATCH 19/22] HWPOISON: detect free buddy pages explicitly Wu Fengguang
2009-06-15 2:45 ` [PATCH 20/22] HWPOISON: collect infos that reflect the impact of the memory corruption Wu Fengguang
2009-06-15 2:45 ` [PATCH 21/22] HWPOISON: send uevent to report " Wu Fengguang
2009-06-15 6:29 ` Andi Kleen
2009-06-15 9:56 ` Wu Fengguang
2009-06-16 0:35 ` Greg KH
2009-06-15 2:45 ` [PATCH 22/22] HWPOISON: FOR TESTING: Enable memory failure code unconditionally Wu Fengguang
2009-06-15 3:18 ` [PATCH 00/22] HWPOISON: Intro (v5) Balbir Singh
2009-06-15 4:27 ` Wu Fengguang
2009-06-15 6:44 ` Nick Piggin [this message]
2009-06-15 7:09 ` Andi Kleen
2009-06-15 7:19 ` Nick Piggin
2009-06-15 12:10 ` Wu Fengguang
2009-06-15 12:25 ` Nick Piggin
2009-06-15 14:22 ` Wu Fengguang
2009-06-17 6:37 ` [RFC][PATCH] HWPOISON: only early kill processes who installed SIGBUS handler Wu Fengguang
2009-06-17 8:04 ` Nick Piggin
2009-06-17 9:55 ` Wu Fengguang
2009-06-17 10:00 ` Nick Piggin
2009-06-17 11:56 ` Wu Fengguang
2009-06-18 9:56 ` Wu Fengguang
2009-06-15 8:14 ` [PATCH 00/22] HWPOISON: Intro (v5) Nick Piggin
2009-06-15 10:09 ` Wu Fengguang
2009-06-15 10:36 ` Nick Piggin
2009-06-15 11:41 ` Wu Fengguang
2009-06-15 12:51 ` Hugh Dickins
2009-06-15 13:00 ` Alan Cox
2009-06-15 13:29 ` Andi Kleen
2009-06-15 13:28 ` H. Peter Anvin
2009-06-15 14:48 ` Alan Cox
2009-06-15 15:24 ` Andi Kleen
2009-06-15 15:28 ` Alan Cox
2009-06-15 16:19 ` Andi Kleen
2009-06-15 16:28 ` Alan Cox
2009-06-15 17:07 ` Andi Kleen
2009-06-16 19:44 ` Russ Anderson
2009-06-16 20:28 ` H. Peter Anvin
2009-06-16 20:54 ` Russ Anderson
2009-06-16 20:58 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090615064447.GA18390@wotan.suse.de \
--to=npiggin@suse.de \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=chris.mason@oracle.com \
--cc=fengguang.wu@intel.com \
--cc=hpa@zytor.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mingo@elte.hu \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).