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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 2 Jan 2012 22:29:20 +0000
From:	Matthew Garrett <mjg@...hat.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Jack Stone <jwjstone@...tmail.fm>,
	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.

On Mon, Jan 02, 2012 at 02:19:37PM -0800, Linus Torvalds wrote:
> On Mon, Jan 2, 2012 at 2:12 PM, Matthew Garrett <mjg@...hat.com> wrote:
> >
> > The kernel that loaded the firmware to make the device work is not
> > required to be the same kernel that we're running when we suspend.
> 
> Why do you make up all these idiotic theoretical cases that nobody
> cares about and has no relevance what-so-ever for the 99%?

Rebooting is a theoretical case?

> And if you *can* load the firmware in the new kernel, just do it
> before the suspend event. Problem solved.

How do we know to do that? The device appears to be a UVC device at 
suspend. It's only at resume that we discover that it's actually a 
programmable device.

> And once more: your made-up scenario has *nothing* what-so-ever to do
> with the actual warnings that started this whole thread.

The warnings that started the thread are associated with a driver that I 
wrote. I'm explaining to you that your suggestion doesn't work for 
a real-world scenario involving that driver. If the firmware has been 
loaded and then the user reboots, the new kernel has no indication that 
it needs to load the firmware. There are various ways of handling this, 
but it's simply untrue that we'll always load the firmware at kernel 
init time.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/