On Monday 13 January 2003 16:16, Alan Stern wrote: > As far as guaranteeing that when usb_unlink_urb() returns from a > synchronous unlink, the completion handler will have already finished -- > so far as I can tell there is currently no such guarantee.
I am a device driver writer. I need this guarantee! I want to use usb_unlink_urb() in order to shut down. And if the completion function might be run after usb_unlink_urb() returns, there may be races because of non-existing data structures. Synchronous == wait until done. If this is not doable, change the API. But make it simple and racefree. Don't introduce exceptions simply because you are lazy. It is a pain. I wish the usb core driver writers would take their heads around and look at the API from the device drivers view. Just me 2 cent best regards Wolfgang Mües ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
