From: Sean Anderson <sean.anderson@linux.dev>
To: Leo Yan <leo.yan@arm.com>
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
Yeoreum Yun <yeoreum.yun@arm.com>,
Mike Leach <mike.leach@linaro.org>,
Linu Cherian <lcherian@marvell.com>,
linux-kernel@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
James Clark <james.clark@linaro.org>
Subject: Re: [PATCH v3] coresight: Fix possible deadlock in coresight_panic_cb
Date: Tue, 16 Sep 2025 12:51:11 -0400 [thread overview]
Message-ID: <42f1c98c-1432-47bb-9203-e878f011ff6e@linux.dev> (raw)
In-Reply-To: <20250916164854.GM12516@e132581.arm.com>
On 9/16/25 12:48, Leo Yan wrote:
> On Tue, Sep 16, 2025 at 12:14:40PM -0400, Sean Anderson wrote:
>
> [...]
>
>> > Could you check if the drafted patch below looks good to you? If so, I
>>
>> As stated above I disagree with a half-hearted removal. If you want to do that,
>> then I will resend v2 done with an rcu list and you can make your own follow-up.
>
> It is fine to disagree, but please don't resend v2 :)
>
> We have plan to refactor locking in CoreSight driver, I will try my
> best to avoid adding new lock unless with a strong reason.
As said above it will be done with an rcu list, so no new lock.
Or I can do this patch but stick the notifier block in csdev as suggested by Suzuki.
--Sean
next prev parent reply other threads:[~2025-09-16 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 15:13 [PATCH v3] coresight: Fix possible deadlock in coresight_panic_cb Sean Anderson
2025-09-15 9:58 ` Leo Yan
2025-09-15 14:31 ` Sean Anderson
2025-09-16 16:00 ` Leo Yan
2025-09-16 16:09 ` Suzuki K Poulose
2025-09-16 16:38 ` Leo Yan
2025-09-16 16:42 ` Suzuki K Poulose
2025-09-16 16:55 ` Leo Yan
2025-09-16 16:14 ` Sean Anderson
2025-09-16 16:48 ` Leo Yan
2025-09-16 16:51 ` Sean Anderson [this message]
2025-09-16 17:17 ` Leo Yan
2025-09-17 8:31 ` Suzuki K Poulose
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42f1c98c-1432-47bb-9203-e878f011ff6e@linux.dev \
--to=sean.anderson@linux.dev \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=james.clark@linaro.org \
--cc=lcherian@marvell.com \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=yeoreum.yun@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.