It seems to me that the following is possible:
- driver (module) registers with USB subsystem
- probe function is called, driver is bound to an interface
- (driver cannot be unloaded now - this is done in sysfs, no?)
- driver fires some urbs
- disconnect is called
in disconnect driver calls usb_unlink_urb to kill urbs in flight,
but this fails for some urbs. Driver decides to follow Dave's
advice and leak memory in this error situation, so it doesn't
free its structures, and exits the disconnect method.
- (driver can be unloaded now).
- (some urbs are still in flight)
- driver is unloaded
- urb finally completes - completion handler is called - but it doesn't exist any more
- we are sad
Or do urbs take a reference to the driver somehow?
I'm interested in 2.5 kernels.
Thanks,
Duncan.
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
