From: Bradley Morgan <include@grrlz.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Kees Cook <kees@kernel.org>,
linux-kernel@vger.kernel.org, Bradley Morgan <include@grrlz.net>
Subject: [PATCH] reboot: don't use cb_data to tell if the static sys-off handler is free
Date: Sun, 26 Jul 2026 22:55:41 +0000 [thread overview]
Message-ID: <20260726225541.13304-1-include@grrlz.net> (raw)
There is one static handler for SYS_OFF_PRIO_PLATFORM, shared by all
modes, so the second platform priority registration has to fail with
-EBUSY. alloc_sys_off_handler() decides that by testing cb_data.
cb_data is caller data though, and nothing says it has to be set. A
registration that passes NULL for it leaves the static handler
looking free, so the next one gets the same struct back while the
first is still live: sys_off_cb and list get overwritten, and the
same notifier_block is registered into a second chain. A
notifier_block has one next pointer, so both chains end up wrong.
register_platform_power_off() always passes the power off callback as
cb_data, which is why this held up when the static handler was added.
Callers using register_sys_off_handler() directly have no such rule.
Test sys_off_cb instead. Every handler has one, it is what the
callback path actually needs, and it is set for as long as the
handler is registered.
Fixes: 587b9bfe0668 ("kernel/reboot: Use static handler for register_platform_power_off()")
Signed-off-by: Bradley Morgan <include@grrlz.net>
---
kernel/reboot.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/reboot.c b/kernel/reboot.c
index f070c5c1103a..42fe2708f5d9 100644
--- a/kernel/reboot.c
+++ b/kernel/reboot.c
@@ -366,7 +366,7 @@ static struct sys_off_handler *alloc_sys_off_handler(int priority)
*/
if (priority == SYS_OFF_PRIO_PLATFORM) {
handler = &platform_sys_off_handler;
- if (handler->cb_data)
+ if (handler->sys_off_cb)
return ERR_PTR(-EBUSY);
} else {
if (system_state > SYSTEM_RUNNING)
--
2.47.3
reply other threads:[~2026-07-26 22:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260726225541.13304-1-include@grrlz.net \
--to=include@grrlz.net \
--cc=akpm@linux-foundation.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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