> 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). > > Apart from this issue, poisoning / unpoisoning the urb on close and > always trying to resubmit in the completion handler seems to solve the > problems at hand (for ftdi at least). 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. Alan -- 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
