Re: [PATCH v5] driver core: enforce device_lock for driver_match_device()

[Jon Hunter]

Hi Danilo,

On 22/01/2026 19:35, Danilo Krummrich wrote:
> On Thu Jan 22, 2026 at 7:58 PM CET, Jon Hunter wrote:
> > On 22/01/2026 18:12, Danilo Krummrich wrote:
> > > With this diff, if I intentionally create a deadlock condition on my machine, I
> > > do see a lockdep splat as expected.
> > >
> > > Anyways, another option would be to attach a hardware debugger (I assume you
> > > have TRACE32 or something available?) and then get a backtrace from the CPU
> > > affected of the deadlock.
> >
> > Unfortunately, these days I don't have such tools available so that's
> > not an option.
>
> Hm..slowly running out of options. :)
>
> I remember you previously said that you can still SSH into the machine? If so,
> can you please share the the first output of
>
> 	echo l > /proc/sysrq-trigger
>
> directly after booting?
>
> Subsequently, can you please also run
>
> 	echo w > /proc/sysrq-trigger
>
> and
>
> 	echo t > /proc/sysrq-trigger

You can find the output of the above commands here:

https://pastebin.com/PuhFURwh

If you search for 'state:D', you can see that various drivers are stuck 
waiting for the mutex. I believe that this all happens because the SPI 
driver crashed during the probe and prevents any further drivers from 
probing.

Jon

--
nvpublic