linux-kernel - Re: [PATCH v2 1/2] x86: mce: kexec: turn off MCE in kexec

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <54F474BD.1010802@gmail.com>
Date:	Mon, 02 Mar 2015 23:33:33 +0900
From:	Naoya Horiguchi <nao.horiguchi@...il.com>
To:	Borislav Petkov <bp@...en8.de>
CC:	Naoya Horiguchi <n-horiguchi@...jp.nec.com>,
	"Luck, Tony" <tony.luck@...el.com>,
	Prarit Bhargava <prarit@...hat.com>,
	Vivek Goyal <vgoyal@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Junichi Nomura <j-nomura@...jp.nec.com>,
	Kiyoshi Ueda <k-ueda@...jp.nec.com>
Subject: Re: [PATCH v2 1/2] x86: mce: kexec: turn off MCE in kexec

On Mon, Mar 02, 2015 at 01:17:01PM +0100, Borislav Petkov wrote:
> On Mon, Mar 02, 2015 at 02:31:19AM +0000, Naoya Horiguchi wrote:
> > And please note that the target of this patch is an MCE when the kernel is
> > already running on kdump code (so crashing happened *not* because of the MCE).
> > In that case, we can expect that kdump works fine if the MCE hits the "kdump
> > shotdown" CPU which are just running cpu_relax() loop, because a 2nd kernel's
> > CPU isn't affected by the MCE (even the CPU failure is fatal one.)
>
> Well, why would you even want to disable MCA then? If all the CPUs are
> offlined, it is very very highly unlikely they'd cause an MCE.

Yes, CPU offlining is one option to keep other CPUs quiet. I'm not sure why
current kexec implementation doesn't offline the other CPUs but just doing
cpu_relax() loop, but my guess is that in some kernel panic situation (like
soft lockup) we want to keep CPUs' status undisturbed to make sure the bug's
info is captured in kdump.

> > If a fatal MCE happens on the CPU running kdump code, there's no reason to
> > try harder to get kdump as you pointed out. In such case, what we can do is
> > to print out a message like "kdump failed due to MCE" and reset the system.
>
> Yes, so a primitive kdump-specific MCE handler would be more viable than
> disabling MCA.

OK.

Thanks,
Naoya Horiguchi
--
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/