Re: [PATCH 6/6] driver-core, libnvdimm: Let device subsystems add local lockdep coverage

2019-06-19 Thread Greg Kroah-Hartman
On Wed, Jun 19, 2019 at 03:21:58PM -0700, Dan Williams wrote: > On Tue, Jun 11, 2019 at 4:40 PM Dan Williams wrote: > > > > For good reason, the standard device_lock() is marked > > lockdep_set_novalidate_class() because there is simply no sane way to > > describe the myriad ways the device_lock()

Re: [PATCH 6/6] driver-core, libnvdimm: Let device subsystems add local lockdep coverage

2019-06-19 Thread Dan Williams
On Tue, Jun 11, 2019 at 4:40 PM Dan Williams wrote: > > For good reason, the standard device_lock() is marked > lockdep_set_novalidate_class() because there is simply no sane way to > describe the myriad ways the device_lock() ordered with other locks. > However, that leaves subsystems that know t

[PATCH 6/6] driver-core, libnvdimm: Let device subsystems add local lockdep coverage

2019-06-11 Thread Dan Williams
For good reason, the standard device_lock() is marked lockdep_set_novalidate_class() because there is simply no sane way to describe the myriad ways the device_lock() ordered with other locks. However, that leaves subsystems that know their own local device_lock() ordering rules to find lock orderi