On Thu, Jul 26, 2012 at 1:23 AM, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote: > > So *if* the only problem wrt the USB hub code comes from this area, IMO, USB hub code may not be the only one because both device_add and device_del can just be run in process context, so any hotplug bus may have this kind of problem since the devices in the bus may be unplugged and plugged again during suspend or experience power loss , then the bus driver may take similar handling policy as USB. > then I think the solution might be as simple as just moving the > "usermodehelper_enable()" up a few lines, with a comment. Something > like the *untested* and whitespace-damaged thing below.. > > Rafael? Who has one of those isight things and has seen the warning to test? I fake one USB device disconnect in reset_resume path and looks the patch is good: the device driver can request firmware successfully in its .probe(). > > Linus > > --- > diff --git a/kernel/power/process.c b/kernel/power/process.c > index 19db29f67558..5bf50e488196 100644 > --- a/kernel/power/process.c > +++ b/kernel/power/process.c > @@ -181,6 +181,12 @@ void thaw_processes(void) > pm_freezing = false; > pm_nosig_freezing = false; > > + /* > + * User mode helper are available again (or will be, > + * modulo scheduling) > + */ > + usermodehelper_enable(); This may wake up tasks earlier than before, not sure if it might have side effects. Thanks, -- Ming Lei -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
