linux-kernel - Re: [PATCH] x86/microcode: Do not select FW

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: <20200610103418.GE14118@zn.tnic>
Date:   Wed, 10 Jun 2020 12:34:18 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Herbert Xu <herbert@...dor.apana.org.au>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        "H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
        x86-ml <x86@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Luis Chamberlain <mcgrof@...nel.org>,
        Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] x86/microcode: Do not select FW_LOADER

On Wed, Jun 10, 2020 at 08:28:51PM +1000, Herbert Xu wrote:
> Because MICROCODE is the only thing on my system that pulls it
> into the kernel.

That's a very interesting system you have.

> That shouldn't be a problem.  That function can simply move under
> another (hidden) Kconfig option that gets selected by both MICROCODE
> and FW_LOADER.

Out Kconfig symbols space is a mess and I'd prefer not to add another
one if there's no good reason for it.

-- 
Regards/Gruss,
    Boris.

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