On Thu, 25 Mar 2004, Matthias Andree wrote: > 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.
The problem was not that the usbmodules program was messing up the kernel -- it wasn't. It was messing up your scanner, by sending too many requests too quickly while another program was using the device and not waiting for the responses. There's nothing unusual about one userspace program being able to mess up another, especially if they both try to access the same device at the same time. On the other hand, it's true that /proc/bus/usb/... could use better access control. In fact, it could be improved in many ways. That's generally been regarded as low-priority stuff, though; there are plenty of more pressing issues to be solved first. Alan Stern ------------------------------------------------------- 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
