From: David Carlier <devnexen@gmail.com>
To: Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>
Cc: linux-kernel@vger.kernel.org, David Carlier <devnexen@gmail.com>
Subject: [PATCH 1/2] sched_ext: Use rcu_dereference() for scx_root in dump paths
Date: Thu, 26 Feb 2026 05:26:39 +0000 [thread overview]
Message-ID: <20260226052640.7191-1-devnexen@gmail.com> (raw)
scx_dump_task() and scx_dump_state() read scx_root directly without
rcu_dereference() or NULL check. If the BPF scheduler is torn down
concurrently, scx_root can become NULL between the read and the
dereference in SCX_HAS_OP(), causing a NULL pointer dereference.
Use rcu_dereference() to properly access scx_root under RCU protection
and bail out early if it is NULL.
Signed-off-by: David Carlier <devnexen@gmail.com>
---
kernel/sched/ext.c | 28 ++++++++++++++++++++++++++--
1 file changed, 26 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/ext.c b/kernel/sched/ext.c
index 9280381f8923..eb539b671c49 100644
--- a/kernel/sched/ext.c
+++ b/kernel/sched/ext.c
@@ -4580,7 +4580,19 @@ static void scx_dump_task(struct seq_buf *s, struct scx_dump_ctx *dctx,
struct task_struct *p, char marker)
{
static unsigned long bt[SCX_EXIT_BT_LEN];
- struct scx_sched *sch = scx_root;
+ struct scx_sched *sch;
+
+ /*
+ * The BPF scheduler can be torn down concurrently
+ */
+ rcu_read_lock();
+ sch = rcu_dereference(scx_root);
+ if (!sch) {
+ rcu_read_unlock();
+ return;
+ }
+ rcu_read_unlock();
+
char dsq_id_buf[19] = "(n/a)";
unsigned long ops_state = atomic_long_read(&p->scx.ops_state);
unsigned int bt_len = 0;
@@ -4623,7 +4635,19 @@ static void scx_dump_state(struct scx_exit_info *ei, size_t dump_len)
{
static DEFINE_SPINLOCK(dump_lock);
static const char trunc_marker[] = "\n\n~~~~ TRUNCATED ~~~~\n";
- struct scx_sched *sch = scx_root;
+ struct scx_sched *sch;
+
+ /*
+ * The BPF scheduler can be torn down concurrently
+ */
+ rcu_read_lock();
+ sch = rcu_dereference(scx_root);
+ if (!sch) {
+ rcu_read_unlock();
+ return;
+ }
+ rcu_read_unlock();
+
struct scx_dump_ctx dctx = {
.kind = ei->kind,
.exit_code = ei->exit_code,
--
2.51.0
next reply other threads:[~2026-02-26 5:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 5:26 David Carlier [this message]
2026-02-26 5:26 ` [PATCH 2/2] sched_ext: Fix TOCTOU on p->scx.dsq in scx_dump_task() David Carlier
2026-02-27 18:33 ` Tejun Heo
2026-02-27 18:41 ` David CARLIER
2026-02-27 18:31 ` [PATCH 1/2] sched_ext: Use rcu_dereference() for scx_root in dump paths Tejun Heo
2026-02-27 19:04 ` David CARLIER
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=20260226052640.7191-1-devnexen@gmail.com \
--to=devnexen@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=void@manifault.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