On Wed, Oct 17, 2018 at 04:40:01PM -0700, Bart Van Assche wrote: > Make sure that a complaint appears in the kernel log if the driver core > locking assumptions are violated. > > Cc: Lee Duncan <[email protected]> > Cc: Hannes Reinecke <[email protected]> > Cc: Luis Chamberlain <[email protected]> > Cc: Johannes Thumshirn <[email protected]> > Cc: Christoph Hellwig <[email protected]> > Cc: Greg Kroah-Hartman <[email protected]> > Signed-off-by: Bart Van Assche <[email protected]> > --- > drivers/base/dd.c | 16 ++++++++++++++++ > drivers/base/memory.c | 4 ++++ > 2 files changed, 20 insertions(+) > > diff --git a/drivers/base/dd.c b/drivers/base/dd.c > index b4212154a94b..033382421351 100644 > --- a/drivers/base/dd.c > +++ b/drivers/base/dd.c > @@ -315,11 +315,15 @@ __exitcall(deferred_probe_exit); > */ > bool device_is_bound(struct device *dev) > { > + lockdep_assert_held(&dev->mutex);
With this patch applied, are you seeing lockdep messages anywhere? thanks, greg k-h
