linux-kernel - Re: [PATCH v3] x86/mce: Try printing all machine check banks known before panic

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: <CANVTcTaz6pZ=oc0omXa-nPD8G3uOfCVKag-VC66x5gNeGkrgvQ@mail.gmail.com>
Date:	Sat, 22 Nov 2014 23:32:00 +0800
From:	rui wang <ruiv.wang@...il.com>
To:	Borislav Petkov <bp@...en8.de>
Cc:	"Luck, Tony" <tony.luck@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"gong.chen@...ux.intel.com" <gong.chen@...ux.intel.com>,
	"Wang, Rui Y" <rui.y.wang@...el.com>
Subject: Re: [PATCH v3] x86/mce: Try printing all machine check banks known
 before panic

On 11/22/14, Borislav Petkov <bp@...en8.de> wrote:
> On Sat, Nov 22, 2014 at 10:16:49AM +0800, rui wang wrote:
>> I think both possibilities are valid. But experiments show that the
>> error logs are not in the dmesg preserved by kdump in /var/crash/
>> after panic and reboot, and not in the mcelog.entry[] array in the
>> kernel. So they must be somewhere in user space memory. Even if we
>> have serial console connected we still can't cache them. The
>> difficulty is that there's no easy way to force a user space daemon to
>> do something during panic.
>>
>> The new banks_saved[] array acts like a safe guard when you pass
>> something to someone else - to prevent it from getting lost in the
>> interim.
>
> ... and instead of duplicating the mcelog functionality partially by
> adding yet another array of struct mces, simply change mcelog to not
> zero out its contents and dump the last 32 errors that passed through
> there.
>

But that means mcelog buffer will have to become circular, and we can
only dump the last 32 errors. There must be a reason why it wasn't
designed as circular. I guess its benefit is as Tony explained: on
systems where mcelog isn't run or run at a later time, we may lose the
first error which is more important.

There's valid reasons why people may not run mcelog, because they may
never see machine checks during their lifetime. However once their
machine panics due to a machine check, it suddenly becomes important.

Thanks
Rui
--
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/