Commit 735ee02
sched_ext: Use WRITE_ONCE() for the write side of scx_enable helper pointer
commit 2fcfe59 upstream.
scx_enable() uses double-checked locking to lazily initialize a static
kthread_worker pointer. The fast path reads helper locklessly:
if (!READ_ONCE(helper)) { // lockless read -- no helper_mutex
The write side initializes helper under helper_mutex, but previously
used a plain assignment:
helper = kthread_run_worker(0, "scx_enable_helper");
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
plain write -- KCSAN data race with READ_ONCE() above
Since READ_ONCE() on the fast path and the plain write on the
initialization path access the same variable without a common lock,
they constitute a data race. KCSAN requires that all sides of a
lock-free access use READ_ONCE()/WRITE_ONCE() consistently.
Use a temporary variable to stage the result of kthread_run_worker(),
and only WRITE_ONCE() into helper after confirming the pointer is
valid. This avoids a window where a concurrent caller on the fast path
could observe an ERR pointer via READ_ONCE(helper) before the error
check completes.
Fixes: b06ccba ("sched_ext: Fix starvation of scx_enable() under fair-class saturation")
Signed-off-by: zhidao su <suzhidao@xiaomi.com>
Acked-by: Andrea Righi <arighi@nvidia.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>1 parent ac8befc commit 735ee02
1 file changed
Lines changed: 5 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
5219 | 5219 | | |
5220 | 5220 | | |
5221 | 5221 | | |
5222 | | - | |
5223 | | - | |
5224 | | - | |
| 5222 | + | |
| 5223 | + | |
| 5224 | + | |
5225 | 5225 | | |
5226 | 5226 | | |
5227 | 5227 | | |
5228 | | - | |
| 5228 | + | |
| 5229 | + | |
5229 | 5230 | | |
5230 | 5231 | | |
5231 | 5232 | | |
| |||
0 commit comments