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  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:	Sun, 1 Jan 2012 22:39:13 +0100
From:	Michael B├╝sch <>
To:	Oliver Neukum <>
Cc:	Linus Torvalds <>,
	Alan Stern <>,
	Matthew Garrett <>,
	Dave Jones <>,
	Linux Kernel <>,
	Larry Finger <>,
	Chaoming Li <>,
	"John W. Linville" <>,
	"Greg Kroah-Hartman" <>,
	USB list <>,
	Linux Wireless List <>
Subject: Re: loading firmware while usermodehelper disabled.

On Sun, 1 Jan 2012 22:27:56 +0100
Oliver Neukum <> wrote:

> Ideally usbcore would deal with such devices, but at present the USB layer
> is unable to cleanly resume devices that change their IDs during
> resume.
> Solving this would mean putting all firmware loaders into kernel space.
> And the mode switching logic as well.

I don't get it. Why would a device enter a state after resume, that it was not
in at _any_ time before the machine was suspended?

These change-id-on-bootstrap devices usually work like this,
as far as I know:

probe bootstrap device (switches hw to real device)
probe real device (firmware is loaded)
Suspend machine
Resume machine
usb detects that the device is "gone"
probe/resume bootstrap device (switches hw to real device)
probe/resume real device (No need to fetch fw from userspace. It's already cached)

What did I get wrong?

Greetings, Michael.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists