From: Bradley Morgan <include@grrlz.net>
To: "Rafael J . Wysocki" <rafael@kernel.org>
Cc: Thierry Reding <treding@nvidia.com>,
Daniel Leznan <daniel.lezcano@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
Valentin Schneider <vschneid@redhat.com>,
Rosen Penev <rosenp@gmail.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] PM: cpu: Restore the RCU grace period to cpu_pm_unregister_notifier()
Date: Thu, 13 Aug 2026 07:43:41 +0000 [thread overview]
Message-ID: <20260813074343.26460-1-include@grrlz.net> (raw)
Since commit b2f6662ac08d ("PM: cpu: Make notifier chain use a
raw_spinlock_t") cpu_pm_unregister_notifier() no longer waits for an
RCU grace period, but cpu_pm_notify() still walks the chain with only
rcu_read_lock() held. A driver that frees its notifier block right
after unregistering can race with a concurrent walker.
Patch 1 moves the one caller that unregisters from atomic context out
from under its spinlock, patch 2 restores the grace period.
Bradley Morgan (2):
clocksource/drivers/timer-ti-dm: Unregister CPU PM notifier outside of
the timer lock
PM: cpu: Restore synchronize_rcu() to cpu_pm_unregister_notifier()
drivers/clocksource/timer-ti-dm.c | 9 ++++++---
kernel/cpu_pm.c | 9 ++++++++-
2 files changed, 14 insertions(+), 4 deletions(-)
--
2.47.3
next reply other threads:[~2026-08-13 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 7:43 Bradley Morgan [this message]
2026-08-13 7:43 ` [PATCH 1/2] clocksource/drivers/timer-ti-dm: Unregister CPU PM notifier outside of the timer lock Bradley Morgan
2026-08-13 7:43 ` [PATCH 2/2] PM: cpu: Restore synchronize_rcu() to cpu_pm_unregister_notifier() Bradley Morgan
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=20260813074343.26460-1-include@grrlz.net \
--to=include@grrlz.net \
--cc=daniel.lezcano@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rosenp@gmail.com \
--cc=tglx@kernel.org \
--cc=treding@nvidia.com \
--cc=vschneid@redhat.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.