linux-kernel - Re: [PATCH] x86/microcode/intel: print previous microcode revision during early update

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: <20180126115800.bvqrzik2f3hmmiah@pd.tnic>
Date:   Fri, 26 Jan 2018 12:58:00 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Petr Oros <poros@...hat.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/microcode/intel: print previous microcode revision
 during early update

On Fri, Jan 26, 2018 at 12:45:35PM +0100, Petr Oros wrote:
> During time of facing the Spectre vulnerability and the requirement of handling
> different microcode updates, it has shown, that it would be useful to have
> additional information which microcode version was in BIOS, if the early-update
> routine will apply an update.

Dmesg tells you if the update was applied or not.

And if you really wanna know the old microcode revision, you can boot
with "dis_ucode_ldr" and do "grep microcode /proc/cpuinfo".

-- 
Regards/Gruss,
    Boris.

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