linux-kernel - Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel, use it in more drivers.

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: <487C0365.5030203@garzik.org>
Date:	Mon, 14 Jul 2008 21:54:45 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Arjan van de Ven <arjan@...radead.org>
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	David Woodhouse <dwmw2@...radead.org>,
	torvalds@...ux-foundation.org, alan@...rguk.ukuu.org.uk,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel,
 use it in more drivers.

Arjan van de Ven wrote:
> On Mon, 14 Jul 2008 16:41:19 -0700
> Andrew Morton <akpm@...ux-foundation.org> wrote:
> 
>> On Mon, 14 Jul 2008 16:23:26 -0700
>> David Woodhouse <dwmw2@...radead.org> wrote:
>>
>>> Linus, please pull from the for-2.6.27 branch of:
>>> 	git://git.infradead.org/users/dwmw2/firmware-2.6.git
>>> for-2.6.27
>> The firmware flamewars seem to have subsided lately.  Is everyone
>> happy with this now?
>>
> 
> this seems to have left the contentious pieces out....

Correction:  It seems to have completely ignored contentious issues, 
which is not the same thing.

It -removes- the ability to build firmware into the kernel module -- a 
currently deployed, highly reliable configuration.

I'm not surprised that fact was snipped in David's submission -- 
wouldn't want to mention that you are unconditionally replacing a 
reliable method of firmware loading with a less reliable one.

Building the firmware into the kernel is far less useful than it 
appears:  often users lack the ability to maintain their own vmlinuz 
kernel image build, but do build updated drivers.  e.g. driver disks for 
Red Hat Enterprise Linux.

IMO the newly added /inability/ to build firmware into kernel modules is 
a clear regression.

	Jeff

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