I feel rather uncomfortable with the situation that one user-space USB program can instrument the kernel to screw another user-space program terminally. I wonder if the /proc/bus/usb stuff should lock out other access while some access is going on.
It certainly should. The thing is, usbfs is rather incestuous with respect to other parts of usbcore, and this particular issue gets wrapped up with a few others ... plus of course it seems like gphoto2 may have been relying on some old bugs.
What I think I'll do is wrap up Alan's more-correct patch with a minor locking update that's been in my queue for some time, and ask you to test the combined patch.
- Dave
------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
