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]

Date:   Thu, 3 Jun 2021 22:48:12 +0000
From:   "BeSerra, Christopher" <beserra@...zon.com>
To:     "Luck, Tony" <tony.luck@...el.com>, Borislav Petkov <bp@...en8.de>
CC:     "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

There are corner cases where the CE count is 0 when a storm occurs.  EDAC completely missed logging CEs.

On 6/1/21, 1:41 PM, "Luck, Tony" <tony.luck@...el.com> wrote:

    CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.



    > 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