linux-kernel - Re: [PATCH RESEND] x86: kernel/microcode_core.c simple

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: <20120508040009.GB30652@gmail.com>
Date:	Tue, 8 May 2012 06:00:10 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:	Borislav Petkov <bp@...en8.de>, "H. Peter Anvin" <hpa@...or.com>,
	Shuah Khan <shuahkhan@...il.com>, mingo@...hat.com,
	tglx@...utronix.de, tigran@...azian.fsnet.co.uk,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RESEND] x86: kernel/microcode_core.c simple_strtoul
 cleanup


* Henrique de Moraes Holschuh <hmh@....eng.br> wrote:

> > Of course, one can iterate over each core in a shell-loop 
> > and write into the reload file to reload ucode after having 
> > updated the ucode image in /lib/firmware but removing and 
> > then modprobing the module is shorter :-)
> 
> Can we PLEASE fix it properly by adding a new node (which is 
> _not_ per-cpu) that requests the microcode core to refresh all 
> cpus?  Preferably by invalidating the microcode cache, THEN 
> fetching each required microcode just once for the first core 
> that needs it, and caching it for use the other cores.  You 
> can leave the (IMHO mostly useless) per-cpu sysfs nodes alone, 
> so as to not break ABI, or deprecate them for an year or 
> something.
> 
> I am speaking this with my userland maintainer hat.  I *do 
> NOT* want to rmmod crap in a production server to update 
> microcode.  And I want to be able to support static-compiled 
> microcode.

Seconded. There's also the ability to disable module unloading.

Thanks,

	Ingo
--
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/