| 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
| ||
|
Date: Thu, 03 Jul 2008 07:34:27 -0400
From: Valdis.Kletnieks@...edu
To: David Woodhouse <dwmw2@...radead.org>
Cc: Tigran Aivazian <tigran@...azian.fsnet.co.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, jonathan@...masters.org,
Shaohua Li <shaohua.li@...el.com>, greg@...ah.com,
Kay Sievers <kay.sievers@...y.org>, arjan@...radead.org
Subject: Re: Intel Microcode loader, tg3 driver, and the -rc8-mmotd New World Order firmware...
On Thu, 03 Jul 2008 11:30:29 BST, David Woodhouse said:
> > Anyhow, it appears the firmware_request() was just a bullet loaded in the
> > chamber waiting for me to pull the trigger 2 years later by setting
> > CONFIG_FIRMWARE_IN_KERNEL=n :)
>
> No, the recent firmware changes haven't modified this. The
> FIRMWARE_IN_KERNEL option makes no difference here.
"D'Oh!" -- H. Simpson.
"Nevermind" - Emily Litella.
Actually, FIRMWARE_IN_KERNEL *did* make a difference - it busticated the tg3
driver and while fighting with the 'firmware: requesting tigon/tg3_tso.bin'
errors I had just inflicted on myself, I found the 'requesting intel-ucode/060f06'
messages as well - and totally failed to notice that the *previous* kernel
and initscripts had *all along* been doing a modprobe, which generated 2 requests
(one per CPU) which failed, and then the initscript ran microcode_ctl *anyhow*,
papering over the two failed requests.. ;)
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists