From: zhidao su <soolaugust@gmail.com>
To: sched-ext@lists.linux.dev
Cc: linux-kernel@vger.kernel.org, tj@kernel.org, void@manifault.com,
arighi@nvidia.com, changwoo@igalia.com, peterz@infradead.org,
mingo@redhat.com, zhidao su <suzhidao@xiaomi.com>
Subject: [PATCH] sched_ext: Use READ_ONCE() for bypass_depth in scx_bypass()
Date: Mon, 23 Mar 2026 19:12:02 +0800 [thread overview]
Message-ID: <20260323111202.3960280-1-suzhidao@xiaomi.com> (raw)
In scx_bypass(), pos->bypass_depth is read under scx_sched_lock to
update per-cpu BYPASSING flags:
raw_spin_lock(&scx_sched_lock);
scx_for_each_descendant_pre(pos, sch) {
if (pos->bypass_depth) /* bare read */
However, bypass_depth is written by inc_bypass_depth() and
dec_bypass_depth() under scx_bypass_lock (a different lock):
lockdep_assert_held(&scx_bypass_lock);
WRITE_ONCE(sch->bypass_depth, sch->bypass_depth + 1);
The read side here holds scx_sched_lock, not scx_bypass_lock, so the
two sides are protected by different locks, constituting a lockless
concurrent access. All other read sites consistently use READ_ONCE():
L1237: if (unlikely(READ_ONCE(sch->bypass_depth)))
L4083: while (likely(!READ_ONCE(sch->bypass_depth)))
Add the missing READ_ONCE() for consistency with the rest of the code
and to make the concurrency intent explicit to KCSAN.
Signed-off-by: zhidao su <suzhidao@xiaomi.com>
---
kernel/sched/ext.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/ext.c b/kernel/sched/ext.c
index 72a07eb050a3..2654690e3661 100644
--- a/kernel/sched/ext.c
+++ b/kernel/sched/ext.c
@@ -5343,7 +5343,7 @@ static void scx_bypass(struct scx_sched *sch, bool bypass)
scx_for_each_descendant_pre(pos, sch) {
struct scx_sched_pcpu *pcpu = per_cpu_ptr(pos->pcpu, cpu);
- if (pos->bypass_depth)
+ if (READ_ONCE(pos->bypass_depth))
pcpu->flags |= SCX_SCHED_PCPU_BYPASSING;
else
pcpu->flags &= ~SCX_SCHED_PCPU_BYPASSING;
--
2.43.0
next reply other threads:[~2026-03-23 11:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 11:12 zhidao su [this message]
2026-03-23 18:41 ` Tejun Heo
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=20260323111202.3960280-1-suzhidao@xiaomi.com \
--to=soolaugust@gmail.com \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sched-ext@lists.linux.dev \
--cc=suzhidao@xiaomi.com \
--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
all inboxes | Powered by JetHome®