Re: [PATCH v3] coresight: Fix possible deadlock in coresight_panic_cb

[Suzuki K Poulose]

On 16/09/2025 17:38, Leo Yan wrote:
> On Tue, Sep 16, 2025 at 05:09:01PM +0100, Suzuki Kuruppassery Poulose wrote:
>
> [...]
>
> > >   From ea78dd22cbdd97f709c5991d5bd3be97be6e137e Mon Sep 17 00:00:00 2001
> > > From: Sean Anderson <sean.anderson@xxxxxxxxx>
> > > Date: Tue, 16 Sep 2025 16:03:58 +0100
> > > Subject: [PATCH] coresight: Fix possible deadlock in coresight_panic_cb()
> > >
> > > coresight_panic_cb() is called during a panic. It invokes
> > > bus_for_each_dev(), which then calls bus_to_subsys() and takes the
> > > 'bus_kset->list_lock'. If a panic occurs after the lock has been
> > > acquired, it can lead to a deadlock.
> > >
> > > Instead of using a common panic notifier to iterate the bus, this commit
> > > directly registers the TMC device's panic notifier. This avoids bus
> > > iteration and effectively eliminates the race condition that could cause
> > > the deadlock.
> >
> > Well, if you are going that far, why not register the notifier from
> > coresight-core ?
>
> I have thought this but gave up.
>
> When register a panic's notifier, it does not provide an argument for
> passing a private data. So the code below uses container_of() to convert
> notifier block pointer to the TMC driver data, as a result, the code is
> specific to TMC driver.

notifier_block in csdev ?