* [PATCH] sched_ext: Use READ_ONCE() for bypass_depth in scx_bypass()
@ 2026-03-23 11:12 zhidao su
2026-03-23 18:41 ` Tejun Heo
0 siblings, 1 reply; 2+ messages in thread
From: zhidao su @ 2026-03-23 11:12 UTC (permalink / raw)
To: sched-ext
Cc: linux-kernel, tj, void, arighi, changwoo, peterz, mingo, zhidao su
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
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: [PATCH] sched_ext: Use READ_ONCE() for bypass_depth in scx_bypass()
2026-03-23 11:12 [PATCH] sched_ext: Use READ_ONCE() for bypass_depth in scx_bypass() zhidao su
@ 2026-03-23 18:41 ` Tejun Heo
0 siblings, 0 replies; 2+ messages in thread
From: Tejun Heo @ 2026-03-23 18:41 UTC (permalink / raw)
To: zhidao su
Cc: sched-ext, linux-kernel, void, arighi, changwoo, peterz, mingo,
zhidao su
Hello,
On Mon, Mar 23, 2026 at 07:12:02PM +0800, zhidao su wrote:
> 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
It's inside scx_bypass() which is holding scx_bypass_lock throughout the
body of the function.
> 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.
Plesae do not send patches to address KCSAN issues unless you can reproduce
KCSAN warnings and always attach the output of KCSAN.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-03-23 18:41 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-03-23 11:12 [PATCH] sched_ext: Use READ_ONCE() for bypass_depth in scx_bypass() zhidao su
2026-03-23 18:41 ` Tejun Heo
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®