[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.01.0906120827020.3237@localhost.localdomain>
Date: Fri, 12 Jun 2009 08:28:42 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Ingo Molnar <mingo@...e.hu>
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>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
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: Re: [PATCH 1/5] HWPOISON: define VM_FAULT_HWPOISON to 0 when feature
is disabled
On Fri, 12 Jun 2009, Ingo Molnar wrote:
>
> This seems like trying to handle a failure mode that cannot be and
> shouldnt be 'handled' really. If there's an 'already corrupted' page
> then the box should go down hard and fast, and we should not risk
> _even more user data corruption_ by trying to 'continue' in the hope
> of having hit some 'harmless' user process that can be killed ...
No, the box should _not_ go down hard-and-fast. That's the last thing we
should *ever* do.
We need to log it. Often at a user level (ie we want to make sure it
actually hits syslog, possibly goes out the network, maybe pops up a
window, whatever).
Shutting down the machine is the last thing we ever want to do.
The whole "let's panic" mentality is a disease.
Linus
--
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