linux-kernel - Re: [PATCH 2/2] x86/microcode: Add a "microcode=" command line option

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: <20230612090617.GAZIbgCcI9PssBgHxF@fat_crate.local>
Date:   Mon, 12 Jun 2023 11:06:17 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Ashok Raj <ashok.raj@...el.com>
Cc:     X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
        Dave Hansen <dave.hansen@...el.com>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 2/2] x86/microcode: Add a "microcode=" command line option

On Fri, Jun 09, 2023 at 08:37:21AM -0700, Ashok Raj wrote:
> Since the code doesn't use this in the early loading, it appears we can
> drop the cmdline entirely?

The driver needs a control mechanism and this is it. It needs to be
always there so no, no debugfs.

> If the user switches the expected flow, should the code "taint" if its
> opted out?

When it turns out that this needs to happen, it'll get added then.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette