Greg KH wrote:
Yes, this is a problem, the module can be unloaded and then the completion fuction can be called.
How? I don't see it. Unless the driver completely violates basic rules like implementing disconnect() correctly, which will break more than just module unloading.
I'm trying to fix up the usb device reference counting logic right now and running into issues where host controllers try to access urbs after their devices have been removed from the system :(
Not supposed to happen ... when they call giveback(), that's supposed to mean they've forgotten about that URB. Is it buggy disconnect() logic, or some HCD calling giveback too early? I think we've known for a long time that it'd be worth auditing the drivers in the 2.5 tree to see if they disconnect() reasonably. - Dave ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
