linux-kernel - Re: [RFC PATCH] x86/mce: Check MCi_STATUS[MISCV] for usable addr on Intel only

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:   Wed, 19 Apr 2017 00:11:13 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     "Ghannam, Yazen" <Yazen.Ghannam@....com>
Cc:     Tony Luck <tony.luck@...el.com>,
        linux-edac <linux-edac@...r.kernel.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] x86/mce: Check MCi_STATUS[MISCV] for usable addr on
 Intel only

On Tue, Apr 18, 2017 at 09:26:03PM +0000, Ghannam, Yazen wrote:
> We definitely don't need to look at MiscV.
> 
> But the value in MCA_ADDR isn't necessarily a system physical address. It can be,
> or it can be a normalized address in the case of UMCs, or it can a set/way for caches.
> So it depends on the bank type and error type.

Right, this is all future work. mce_usable_address() would need some
beefing up then.

> All this may just be for SMCA systems though. I need to double check.

Thanks!

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.