On Mon, Nov 06, 2017 at 01:32:19AM +0000, Bryan O'Donoghue wrote: > 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 <pure.lo...@nexus-software.ie> > Cc: Johan Hovold <jo...@kernel.org> > Cc: Alex Elder <el...@kernel.org> > Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org> > Cc: Mitch Tasman <tas...@leaflabs.com> > Cc: greybus-...@lists.linaro.org > Cc: de...@driverdev.osuosl.org > Cc: linux-ker...@vger.kernel.org > ---
This looks like it addresses both my comments on v1 (mutex and error stats). Thanks for tracking it down. Reviewed-by: Johan Hovold <jo...@kernel.org> Johan _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel