On Thursday 11 October 2012 11:18:22 Ming Lei wrote: > On Wed, Oct 10, 2012 at 1:51 PM, Oliver Neukum <oneukum@xxxxxxx> wrote: > > > > No, the problem is autoresume. > > > > Suppose we have a device with two interface. Interface A be usbnet; interface B > > something you page on. Now consider that you can only resume both interfaces > > and this is (and needs to be) done synchronously. > > > > Now we can have this code path: > > > > autoresume of device -> resume() -> kmalloc(..., GFP_KERNEL) -> > > VM layer decides to start paging out -> IO to interface B -> autoresume of device > > --> DEADLOCK > > Currently scsi disk can only be runtime suspended when the device is not > opened, so are you sure that the paging out above can cause IO on a suspend > usb mass storage disk which is not mounted or opened by utility now? We definitely do not wish to keep it that way. People at Intel are currently working on better power management for sd, which would allow full autosuspend. Regards Oliver -- 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
