linux-kernel - Re: [PATCH] x86/microcode: Add an option to reload microcode even if revision is unchanged

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <D8A3D2BD-1FD4-4183-8663-3EF02A6099F3@alien8.de>
Date:   Thu, 05 Sep 2019 00:12:29 +0200
From:   Boris Petkov <bp@...en8.de>
To:     Boris Ostrovsky <boris.ostrovsky@...cle.com>,
        "Raj, Ashok" <ashok.raj@...el.com>
CC:     Mihai Carabas <mihai.carabas@...cle.com>,
        "H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
        Jon Grimm <Jon.Grimm@....com>, kanth.ghatraju@...cle.com,
        konrad.wilk@...cle.com, patrick.colp@...cle.com,
        Thomas Gleixner <tglx@...utronix.de>,
        Tom Lendacky <thomas.lendacky@....com>,
        x86-ml <x86@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/microcode: Add an option to reload microcode even if revision is unchanged

On September 5, 2019 12:06:54 AM GMT+02:00, Boris Ostrovsky <boris.ostrovsky@...cle.com> wrote:
>Why do we need to taint kernel here? We are not making any changes.

Because this is not a normal operation we want users to do. This is only for testing microcode quicker.

>This won't allow people to load from new microcode blob which I thought
>was one of the objectives behind this new feature.

You load a new blob the usual way: echo 1 > ...

This is the "unusual" way where you reload an already loaded revision only.

-- 
Sent from a small device: formatting sux and brevity is inevitable.