linux-kernel - Re: [PATCH 2/6] x86/microcode: Merge early loader

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]

Date:	Mon, 9 Nov 2015 10:42:13 +0100
From:	Harald Hoyer <harald@...hat.com>
To:	Borislav Petkov <bp@...en8.de>,
	Josh Boyer <jwboyer@...oraproject.org>
Cc:	Laura Abbott <labbott@...hat.com>, X86 ML <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/6] x86/microcode: Merge early loader

Am 06.11.2015 um 20:31 schrieb Borislav Petkov:
> On Fri, Nov 06, 2015 at 02:22:42PM -0500, Josh Boyer wrote:
>> So this broke dracut.  Dracut will look at the config file for the
>> INTEL or AMD early config options being set.
> 
> Nothing outside the kernel should depend on Kconfig symbols.
> 
>> Do we have suggestions on how to work this out going forward?  I
>> suppose we could assume the check should only be done on 4.3 or older
>> kernels, but I'm not sure making assumptions about newer kernels is a
>> great idea either.
> 
> How about always adding AMD and Intel microcode always? Maybe with a
> switch to disable adding any microcode for testing purposes only...
> 

Will this work with kernels not supporting the microcode loading?
Theoretically the old kernels would just unpack all cpios one after the other,
right?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/