linux-kernel - RE: [RFC PATCH] x86/mce: Provide sysfs interface to show CMCI storm state

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: <1cc039a15b4248e1a625dbb6fc275169@intel.com>
Date:   Tue, 1 Jun 2021 20:40:34 +0000
From:   "Luck, Tony" <tony.luck@...el.com>
To:     Borislav Petkov <bp@...en8.de>
CC:     Christopher BeSerra <beserra@...zon.com>,
        "x86@...nel.org" <x86@...nel.org>,
        "linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [RFC PATCH] x86/mce: Provide sysfs interface to show CMCI storm
 state

> But I'm unclear as to what this whole use case is. The very first
> "Scripts that process error logs" already sounds like a bad idea - I'd
> expect userspace consumers to open the trace_mce_record() and get the
> MCE records from there. And in that case CMCI storm shouldn't matter...

I think the problem is knowing that many errors are being missed because
of the switch to poll mode. All methods to track errors, including the trace_mce_record()
technique are equally affected by missed errors.

But maybe Chris can better describe what the problem is ...

-Tony