staging: greybus: loopback: Hold per-connection mutex across operations
authorBryan O'Donoghue <[email protected]>
Mon, 6 Nov 2017 01:32:19 +0000 (01:32 +0000)
committerGreg Kroah-Hartman <[email protected]>
Mon, 6 Nov 2017 15:41:22 +0000 (16:41 +0100)
commit5a70524bbf3b2764a2e2cd32f5109fd22c8a135f
tree3a1ae8205f7cf167b132bc19d2b408bf406ab8f4
parent31408d16c21bf19587bf7c862354ea1b37a2ed9c
staging: greybus: loopback: Hold per-connection mutex across operations

Commit d9fb3754ecf8 ("greybus: loopback: Relax locking during loopback
operations") changes the holding of the per-connection mutex to be less
restrictive because at the time of that commit per-connection mutexes were
encapsulated by a per-driver level gb_dev.mutex.

Commit 8e1d6c336d74 ("greybus: loopback: drop bus aggregate calculation")
on the other hand subtracts the driver level gb_dev.mutex but neglects to
move the mutex back to the place it was prior to commit d9fb3754ecf8
("greybus: loopback: Relax locking during loopback operations"), as a
result several members of the per connection struct gb_loopback are racy.

The solution is restoring the old location of mutex_unlock(&gb->mutex) as
it was in commit d9fb3754ecf8 ("greybus: loopback: Relax locking during
loopback operations").

Fixes: 8e1d6c336d74 ("greybus: loopback: drop bus aggregate calculation")
Signed-off-by: Bryan O'Donoghue <[email protected]>
Reviewed-by: Johan Hovold <[email protected]>
Cc: Alex Elder <[email protected]>
Cc: Mitch Tasman <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
drivers/staging/greybus/loopback.c