linux-kernel - Re: [PATCH 1/2] x86: Track minimum microcode revision globally v2

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: <20120613065525.GA12814@liondog.tnic>
Date:	Wed, 13 Jun 2012 08:55:25 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Andi Kleen <ak@...ux.intel.com>, x86@...nel.org, hpa@...or.com,
	eranian@...gle.com, linux-kernel@...r.kernel.org,
	a.p.zijlstra@...llo.nl
Subject: Re: [PATCH 1/2] x86: Track minimum microcode revision globally v2

On Wed, Jun 13, 2012 at 12:53:44AM +0200, Andi Kleen wrote:
> I would consider that a BIOS bug.

Ok, but does the user need to know this? If it is of only informative
nature, he can find out each core's ucode version from /proc/cpuinfo so
why do we need to issue this at boot?

-- 
Regards/Gruss,
    Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/