linux-kernel - Re: [PATCH] x86, mce: reset kernel for no-match exception errors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4A964D01.4090608@linux.intel.com>
Date:	Thu, 27 Aug 2009 11:08:17 +0200
From:	Andi Kleen <ak@...ux.intel.com>
To:	Jin Dongming <jin.dongming@...css.fujitsu.com>
CC:	"H.Peter Anvin" <hpa@...or.com>,
	LKLM <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Huang Ying <ying.huang@...el.com>,
	Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>
Subject: Re: [PATCH] x86, mce: reset kernel for no-match exception errors

Jin Dongming wrote:
> The last case of severity table is used for no match exception error.
> Maybe such kind of error could not happen. But I think when the error
> really happened, the kernel should be reset. Because such error is
> unknown and unexpected. So I make this patch for fixing this problem.

I don't think panicing for a non-signalled error is the correct action.

In general I tried to be conservative regarding panics, this seems
to be too liberal with them.

-Andi
--
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/