[char-misc-next 1/2] mei: bus: use correct lock ordering

2015-10-28 Thread Tomas Winkler
The correct lock order is cl_bus_lock device_lock me_clients_rwsem This order was violated in bus rescan and remove routines when me_client_rwsem was locked before cl_bus_lock. Chain exists of: [4.321653] >device_lock --> >me_clients_rwsem --> >cl_bus_lock [4.321653] [

[char-misc-next 1/2] mei: bus: use correct lock ordering

2015-10-28 Thread Tomas Winkler
The correct lock order is cl_bus_lock device_lock me_clients_rwsem This order was violated in bus rescan and remove routines when me_client_rwsem was locked before cl_bus_lock. Chain exists of: [4.321653] >device_lock --> >me_clients_rwsem --> >cl_bus_lock [4.321653] [