Oliver Neukum wrote: >>Turns out that if the disconnect() method uses synchronous >>unlinks, and the device connects through the shared HCD >>framework, there's a guarantee that the completion routine >>has returned (your other issue!) before usb_unlink_urb() >>does ... unless the urb was already being returned to the >>driver. ... > > The issue is solved if the unlink succeeds. > If however the completion is called due to some > other reason, the unlink will fail. But there's no way > to know that the completion handler has finished. In practice that'd be extremely rare, only showing up on SMP, and even there only the timing is Just Right. Likely just spinning long enough -- udelay(1) is more than enough for most drivers -- for the completion to finish would address the issue.
Did you have some solution to that exotic race? If not, it's not worth worrying about. - 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
