Re: [PATCH] sched_ext: Use READ_ONCE() for bypass_depth in scx_bypass()

[Tejun Heo]

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