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]

Message-ID: <3908561D78D1C84285E8C5FCA982C28F3A0F7606@ORSMSX114.amr.corp.intel.com>
Date:	Tue, 31 May 2016 18:18:42 +0000
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Borislav Petkov <bp@...en8.de>
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.

> 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 between generations?
>
> Something like
>
>	m.bank = -1;
>
> or so?

That might be a bit more obvious than my subtle "one more than possible
on this platform" magic number.

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

Intel is stuck at 32 unless we come up with a new mechanism and change
all the code that generates MSR numbers with "base + 4*i". There are
some virtualization MSRs allocated at what would be bank32.

-Tony