On Mon, 17 Mar 2003, David Brownell wrote: > > Indeed there is a problem. Yet we cannot simply change them all to use > > interruptible sleep. You cannot stop in the middle of usb_reset_device() > > or similar calls. > > Only done by SCSI EH handler threads for now though, yes? > Those could have a "block all signals" policy if it wants; > maybe it does so already.
Yes it does. (Unless it has changed since I last looked at it.) > The same kind of thing holds true for khubd and enumeration. Any > task doing a config change (like set_interface) should block signals, > but otherwise I suspect all synchronous calls should be interruptible > by default ... though someone ought to look for other cases where > that's not true. > > > > Should we simply add a flag to the synchronous calls or add interruptible > > versions? > > Aren't those two options identical? Both are API syntax changes. :) I agree with David's proposal above; just make usb_bulk_msg() and usb_control_msg() interruptible. But what about synchronous usb_unlink_urb()? Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for? http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
