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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 23 Jan 2017 13:51:57 +0100 From: Borislav Petkov <bp@...en8.de> To: Xunlei Pang <xlpang@...hat.com> Cc: x86@...nel.org, linux-kernel@...r.kernel.org, kexec@...ts.infradead.org, Tony Luck <tony.luck@...el.com>, Ingo Molnar <mingo@...hat.com>, Dave Young <dyoung@...hat.com>, Prarit Bhargava <prarit@...hat.com>, Junichi Nomura <j-nomura@...jp.nec.com>, Kiyoshi Ueda <k-ueda@...jp.nec.com>, Naoya Horiguchi <n-horiguchi@...jp.nec.com> Subject: Re: [PATCH] x86/mce: Keep quiet in case of broadcasted mce after system panic On Mon, Jan 23, 2017 at 04:01:51PM +0800, Xunlei Pang wrote: > We met an issue for kdump: after kdump kernel boots up, > and there comes a broadcasted mce in first kernel, the How does that even happen? Lemme try to understand this correctly: the first kernel gets an MCE, kdump starts and boots a *whole* kernel and *then* you get the broadcasted MCE? I have real hard time believing that. What happened to the approach of clearing CR4.MCE before loading the kdump kernel, in native_machine_shutdown() or wherever does the kdump gets loaded... -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists