> As I see it, we've got a bunch of things that need locking protection,
> including:
>
> 1. connect and disconnect events (device creation and deletion
> and also address-0 handling);
> 2. driver probe() and disconnect() calls, also binding and
> unbinding events;
> 3. configuration and related device state changes.
>
> Is it now generally accepted that usb_bus_type.subsys.rwsem is the correct
> lock for 1 and 2? Likewise, is it accepted that dev->serialize is the
> correct lock for 3?
No,
all these operations need to be mutually exclusive. Therefore they need a
common lock, which as things stand, would be subsys.rwsem.
Regards
Oliver
-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
