linux-kernel - Re: [PATCH] x86/mce: Do not use bank 1 for APEI generated error logs.

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:	Tue, 31 May 2016 20:09:00 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	"Luck, Tony" <tony.luck@...el.com>
Cc:	"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Aristeu Rozanski <arozansk@...hat.com>
Subject: Re: [PATCH] x86/mce: Do not use bank 1 for APEI generated error logs.

On Tue, May 31, 2016 at 05:11:45PM +0000, Luck, Tony wrote:
> Because that is DDR3/DDR4 "bank" (internal DIMM detail) as opposed
> to machine check "bank" (CPU microarchitecture detail). We need the
> latter here.

Ok, I see.

Btw, would it have any benefit of writing a "magic" value in m.bank
to denote the error comes from APEI instead of number of banks which
differs betweem generations?

Something like

	m.bank = -1;

or so?

255 banks will never happen anyway! (Famous last words ... :-)))

-- 
Regards/Gruss,
    Boris.

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