On Mon, 30 Jul 2007, Pete Zaitcev wrote: > I am afraid that drivers call unlink left and right, even on URBs which > were not submitted and thus have ->ep == NULL. But on the other hand, > maybe we want to catch them...
That's a good point. I'll add a test to one of the upcoming patches to check for !urb->ep. To some extent drivers have to take responsibility for using usb_unlink_urb() correctly. For example, calling it long after the URB has completed and the device has been unplugged is liable to cause problems because of the stale device pointer. I don't think there's much the core can do about this. Alan Stern ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
