linux-kernel - Re: loading firmware while usermodehelper disabled.

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: <089f1112-758b-4006-ba47-64ce4bc1409f@email.android.com>
Date:	Tue, 03 Jan 2012 00:41:34 +0000
From:	Jack Stone <jwjstone@...tmail.fm>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Matthew Garrett <mjg@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Alan Stern <stern@...land.harvard.edu>,
	Oliver Neukum <oliver@...kum.org>,
	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Larry Finger <Larry.Finger@...inger.net>,
	Chaoming Li <chaoming_li@...lsil.com.cn>,
	"John W. Linville" <linville@...driver.com>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	USB list <linux-usb@...r.kernel.org>,
	Linux Wireless List <linux-wireless@...r.kernel.org>
Subject: Re: loading firmware while usermodehelper disabled.



Alan Cox <alan@...rguk.ukuu.org.uk> wrote:

>> So we have a table of USB ids that list the devices that need
>firmware drivers. When the uvcvideo driver registers the firmware
>interface with a USB id that matches the list we load the firmware
>driver and pass it a "warm start" event so it can cache the firmware.
>> 
>> As long as we can identify the devices that *might* need firmware
>then we are ok.
>
>You just broke the module loading guarantees that stop it all coming
>apart
>in the first place. Probably not in many real world ways but not good.
>
>If we warm booted from Windows into Linux and then suspended then on
>resume we won't have the driver for the firmware loaded present - we
>never saw the 'need firmware' id.

I agree we won't see the need firmware id but we should still be able to identify the device from some of its ids shouldn't we? We could then cache the firmware even though we never loaded it.

>That moves us from a dependancy chain for firmware to one including
>firmware and modules (imagine /lib/modules over iscsi for an iscsi
>adapter needing firmware).
>
>At the moment I don't think anyone has been dumb enough to do firmware
>requiring storage and NFS root over firmware requiring USB devices is
>pretty dumb. I don't however think it's a good hole to dig ?

I'm sure someone will try it at somepoint...

Thanks,

Jack

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
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/