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] [day] [month] [year] [list]

Message-ID: <1518033920.1872.23.camel@redhat.com>
Date:   Wed, 07 Feb 2018 21:05:20 +0100
From:   Stanislav Kozina <skozina@...hat.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Petr Oros <poros@...hat.com>, 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


> Now let's take a step back: you don't really need the previous revision
> in the spectre case! Not really.

I understand all your points.

We submitted the patch to ease debugging of microcode issues where the
systems impacted are not yet identified and thus can't be blacklisted.

Best Regards,
-Stanislav