linux-kernel - Re: [RFC PATCH 0/8] EDAC, mce_amd: Add a tracepoint for the decoded error

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:   Fri, 28 Jul 2017 09:20:52 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     "Luck, Tony" <tony.luck@...el.com>
Cc:     Ingo Molnar <mingo@...nel.org>,
        linux-edac <linux-edac@...r.kernel.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Yazen Ghannam <Yazen.Ghannam@....com>, X86 ML <x86@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 0/8] EDAC, mce_amd: Add a tracepoint for the decoded
 error

On Thu, Jul 27, 2017 at 04:42:19PM +0000, Luck, Tony wrote:
> s/common errors/architectural errors/
> 
> That means we don't need to keep updating for every Xeon that documents
> some MCi_STATUS.MSCOD bits.  Decoding the MCACOD bits will explain
> which component is involved (cache, bus, memory) and some detail on the
> type of access.

Yeah, exactly. Let's take care of the low-hanging fruits first.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--