From: Mohamed Ayman <mohamedaymanworkspace@gmail.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@arm.com>,
James Clark <james.clark@linaro.org>, Leo Yan <leo.yan@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <clrkwllms@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
coresight@lists.linaro.org (moderated list:ARM/CORESIGHT
FRAMEWORK AND DRIVERS),
linux-arm-kernel@lists.infradead.org (moderated
list:ARM/CORESIGHT FRAMEWORK AND DRIVERS),
linux-kernel@vger.kernel.org (open list),
linux-rt-devel@lists.linux.dev (open list:Real-time Linux
(PREEMPT_RT):Keyword:PREEMPT_RT)
Cc: Mohamed Ayman <mohamedaymanworkspace@gmail.com>,
coresight@lists.linaro.org (moderated list:ARM/CORESIGHT
FRAMEWORK AND DRIVERS),
linux-arm-kernel@lists.infradead.org (moderated
list:ARM/CORESIGHT FRAMEWORK AND DRIVERS),
linux-kernel@vger.kernel.org (open list),
linux-rt-devel@lists.linux.dev (open list:Real-time Linux
(PREEMPT_RT):Keyword:PREEMPT_RT)
Subject: [PATCH v3] coresight: Fix scheduling while atomic in coresight_cpu_pm_notify()
Date: Fri, 17 Jul 2026 00:41:54 +0300 [thread overview]
Message-ID: <20260716214155.2049564-1-mohamedaymanworkspace@gmail.com> (raw)
In-Reply-To: <20260712210446.14290-1-mohamedaymanworkspace@gmail.com>
Dropping the last reference to a coresight_device can trigger a kernel
panic on PREEMPT_RT builds due to a "scheduling while atomic" violation.
When the CPU enters an idle state, coresight_cpu_pm_notify() is invoked
with local interrupts disabled. It calls coresight_cpu_get_active_path(),
which currently uses coresight_get_percpu_source_ref() to get a kobject
reference, and then immediately drops it with coresight_put_percpu_source_ref().
If this put_device() call drops the very last reference (e.g., due to a
concurrent device unregistration), it synchronously triggers the release
cascade. On PREEMPT_RT, free_percpu() takes a sleeping rt-mutex.
Furthermore, any parent device in the release chain might also acquire
sleeping locks, causing a system crash in the atomic PM context.
Fix this by eliminating the get/put dance entirely in the PM notifier path.
Since coresight_cpu_pm_notify() runs with IRQs disabled, it is safe to
read the per-cpu source pointer directly under the coresight_dev_lock,
check the mode, and return the path without unnecessarily manipulating the
kobject refcount.
Suggested-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Mohamed Ayman <mohamedaymanworkspace@gmail.com>
---
drivers/hwtracing/coresight/coresight-core.c | 22 ++++++--------------
1 file changed, 6 insertions(+), 16 deletions(-)
diff --git a/drivers/hwtracing/coresight/coresight-core.c b/drivers/hwtracing/coresight/coresight-core.c
index 6d65c43d5..713bcff53 100644
--- a/drivers/hwtracing/coresight/coresight-core.c
+++ b/drivers/hwtracing/coresight/coresight-core.c
@@ -1850,25 +1850,15 @@ static void coresight_release_device_list(void)
static struct coresight_path *coresight_cpu_get_active_path(enum cs_mode mode)
{
struct coresight_device *source;
- bool is_active = false;
+ struct coresight_path *path = NULL;
- source = coresight_get_percpu_source_ref(smp_processor_id());
- if (!source)
- return NULL;
-
- if (coresight_get_mode(source) & mode)
- is_active = true;
+ guard(raw_spinlock_irqsave)(&coresight_dev_lock);
- coresight_put_percpu_source_ref(source);
+ source = per_cpu(csdev_source, smp_processor_id());
+ if (source && (coresight_get_mode(source) & mode))
+ path = source->path;
- /*
- * It is expected to run in atomic context or with the CPU lock held for
- * sysfs mode, so it cannot be preempted to disable the path. Here
- * returns the active path pointer without concern that its state may
- * change. Since the build path has taken a reference on the component,
- * the path can be safely used by the caller.
- */
- return is_active ? source->path : NULL;
+ return path;
}
/* Return: 1 if PM is required, 0 if skip, or a negative error */
--
2.34.1
next prev parent reply other threads:[~2026-07-16 21:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 21:04 [PATCH] coresight: Fix scheduling while atomic in coresight_device_release() Mohamed Ayman
2026-07-13 3:07 ` Jie Gan
2026-07-13 23:00 ` [PATCH v2] coresight: Fix scheduling while atomic in coresight_put_percpu_source_ref() Mohamed Ayman
2026-07-14 10:42 ` Sebastian Andrzej Siewior
2026-07-14 19:42 ` MOHAMED AYMAN
2026-07-15 6:58 ` Sebastian Andrzej Siewior
2026-07-16 3:07 ` MOHAMED AYMAN
2026-07-16 12:32 ` Sebastian Andrzej Siewior
2026-07-16 21:41 ` Mohamed Ayman [this message]
2026-07-17 8:14 ` [PATCH v3] coresight: Fix scheduling while atomic in coresight_cpu_pm_notify() Sebastian Andrzej Siewior
2026-07-17 10:49 ` Leo Yan
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=20260716214155.2049564-1-mohamedaymanworkspace@gmail.com \
--to=mohamedaymanworkspace@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=james.clark@linaro.org \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=mike.leach@arm.com \
--cc=rostedt@goodmis.org \
--cc=suzuki.poulose@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox