> That leads to the question of how to assure that the device doesn't go > away before usb_set_configuration is called. Perhaps > usb_set_configuration and usb_unbind_interface should be changed to > require the caller to hold the serialize lock.
How about __usb_set_configuration - lockless version usb_set_configuration - locked version ? By the way, here is the list of routines that cause trouble for usbfs: usb_probe_interface usb_reset_device usb_set_configuration usb_unbind_interface Both usb_set_configuration and usb_unbind_interface can be trivially modified to have a __ form. usb_probe_interface and usb_reset_device require thought. All the best, Duncan. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
