On Sun, 27 Sep 2009, Alan Cox wrote: > > This case could be handled in the drivers' unthrottle() by checking the > > ASYNC_CLOSING before resubmitting (or, in the ftdi case, adding to the > > work queue). usb-serial.c should check ASYNCB_INITIALIZED instead of port->port.count... > What backtrace do you get from the WARN_ON when that occurs. I'm trying > to work out how it happens in the first place because really it would be > better if it simply didn't happen at all. or else it shouldn't bother to check anything at all. Alan Stern -- 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
