> > But the drivers' ID tables are part of the module ... > > what's the locking being done to prevent rmmod > > during the usb_match_id() call? > > On 2.5 it is protected, once the module subsystem patches are in, by > usb_match_id() not sleeping.
And you're expecting every probe() to not sleep? That's not reasonable. Or were you expecting every probe() to guard itself against module unload? That seems undesirable. I'd expect one of the basic goals would be to shift that responsibility out of drivers (where it will be done N times, not always right) into the usbcore framework (where it's done once, right). - Dave _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
