Am Montag, 2. August 2004 17:14 schrieb Alan Stern:
> There is indeed a problem, but it's not solved so easily.
>
> Consider this instead:
>
> (A) User process uses libusb or /proc/bus/usb/devices or whatever
> to determine what the configuration is and what interfaces exist.
>
> (B) Someone else changes the configuration.
>
> (C) The first process submits an URB to one of the old endpoints.
>
> You can see that once (B) has happened it's already too late to fix
> things, and this is _before_ you have even received the ioctl for (C)!
It cannot be solved at all. You have to open the device _before_ you
determine configuration. Anything else is an unfixable race condition
However, if you've correctly claimed an interface, usbfs can react with
ENODEV.
Regards
Oliver
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
