linux-kernel - Re: [PATCH 2/2] x86, microcode: Ensure that module is only loaded for

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: <CAPXgP12_k4D-r=HQy3zidHhMP8ygMsT4J5Q+-h0CE3k_vpsazA@mail.gmail.com>
Date:	Tue, 17 Apr 2012 18:02:54 +0200
From:	Kay Sievers <kay@...y.org>
To:	Gene Heskett <gene.heskett@...il.com>
Cc:	Borislav Petkov <bp@...64.org>,
	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Andreas Herrmann <andreas.herrmann3@....com>,
	Dave Jones <davej@...hat.com>, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	tigran@...azian.fsnet.co.uk, hpa@...or.com, x86@...nel.org
Subject: Re: [PATCH 2/2] x86, microcode: Ensure that module is only loaded for

2012/4/17 Gene Heskett <gene.heskett@...il.com>:

> I do not think the above has anything to do with the current version
> shipping in some distro's, which is trying to find the intel code on
> kernels >2.6.39 when running on AMD stuff, so that script in /etc/init.d
> needs attention too.  I have nuked about half of that script in my local
> copy so that it does install AMD code on AMD processors.  The errors I was
> seeing were only the lack of its ability to find the Intel code and does
> not generate any output resembling the above.

Just a note: the intel microcode is loaded by a kernel-initiated
firmware request these days. There is no (broken) init script on
recent systems, to (rather mindlessly) fiddle around in userspace with
kernel internals.

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