* [PATCH v3 sched_ext/for-7.4-fixes] sched_ext: Fix stale pick when a wakeup resets the donor during dispatch
@ 2026-10-31 1:54 Tejun Heo
2026-10-31 2:19 ` sashiko-bot
2026-10-31 7:58 ` Andrea Righi
0 siblings, 2 replies; 3+ messages in thread
From: Tejun Heo @ 2026-10-31 1:54 UTC (permalink / raw)
To: sched-ext
Cc: David Vernet, Andrea Righi, Changwoo Min, Emil Tsalapatis,
David Dai, linux-kernel, Tejun Heo
With proxy execution, do_pick_task_scx() passes rq->donor to dispatch_one()
as @prev. Unlike rq->curr, the donor can be moved to another CPU by a wakeup
while dispatch_one() has the rq lock dropped:
1. dispatch_one() drops the rq lock, e.g. to move a task from another CPU.
2. Another CPU wakes the donor, which proxy execution migrated to this CPU.
proxy_needs_return() dequeues it and resets the donor to rq->curr, and
the wakeup enqueues it, possibly on another CPU.
3. dispatch_one() sees @prev queued and returns SCX_DSP_PREV.
4. do_pick_task_scx() returns @prev, and this CPU runs a task that is queued
on another rq.
sched_proxy_block_task() resets the donor the same way when another CPU sets
@prev's policy to SCHED_EXT or moves it to another BPF scheduler, and blocks
@prev instead.
Whatever dispatch concluded, and whatever it does with @prev after the drop,
is about a task this CPU no longer owns. rq_modified_above() catches the
reset only when rq->curr is in a class above ext, and the dl_server pick
skips the check.
Restart the pick when @prev is no longer the donor, as dispatch_core_pick()
already does after a lock drop. dispatch_one() tests after each step that
can drop the lock, and scx_dispatch_sched() decides per ops.dispatch() call
whether to hand @prev over, which also covers a class or scheduler change
across a drop. The donor only ever changes to rq->curr during a pick, so the
retried pick can't go stale again.
7a3a6bfbd62a ("sched: Rework prev_balance() to avoid stale prev references")
closed the same window in prev_balance() by reading rq->donor instead of
taking @prev. That doesn't work here, as the dispatch never evaluated
rq->curr, which may not even be a sched_ext task.
Verified with a synthetic reproducer.
v2: Also cover rq lock drops inside dispatch (sashiko).
v3: Don't keep a stale @prev after ops.dispatch() (sashiko).
Fixes: c6fe97c34a1a ("sched: Allow enabling proxy exec with sched_ext")
Signed-off-by: Tejun Heo <tj@kernel.org>
---
kernel/sched/ext/ext.c | 20 +++++++++++++++++++-
kernel/sched/ext/inlines.h | 33 +++++++++++++++++++++++++++++----
2 files changed, 48 insertions(+), 5 deletions(-)
diff --git a/kernel/sched/ext/ext.c b/kernel/sched/ext/ext.c
index cd923f9f1f2a..43cf98c1d511 100644
--- a/kernel/sched/ext/ext.c
+++ b/kernel/sched/ext/ext.c
@@ -3407,6 +3407,12 @@ static enum scx_dsp_verdict dispatch_one(struct rq *rq, struct task_struct *prev
rq->scx.cpu_released = false;
}
+ /* the ecaps sync may have dropped the rq lock */
+ if (scx_dsp_prev_stale(rq, prev)) {
+ verdict = SCX_DSP_RETRY;
+ goto out;
+ }
+
if (prev->sched_class == &ext_sched_class) {
update_curr_scx(rq);
@@ -3449,8 +3455,19 @@ static enum scx_dsp_verdict dispatch_one(struct rq *rq, struct task_struct *prev
}
verdict = scx_dispatch_sched(root_sch, rq, prev, false);
- if (verdict != SCX_DSP_NONE)
+
+ /* scx_dispatch_sched() may have dropped the rq lock */
+ if (scx_dsp_prev_stale(rq, prev))
+ verdict = SCX_DSP_RETRY;
+
+ switch (verdict) {
+ case SCX_DSP_RETRY:
+ goto out;
+ case SCX_DSP_NONE:
+ break;
+ default:
goto has_tasks;
+ }
/*
* Didn't find another task to run. Keep running @prev unless its own
@@ -3517,6 +3534,7 @@ static enum scx_dsp_verdict dispatch_one(struct rq *rq, struct task_struct *prev
rq->scx.nr_immed))
scx_schedule_reenq_local(rq, 0);
+out:
rq->scx.flags &= ~SCX_RQ_IN_DISPATCH;
return verdict;
}
diff --git a/kernel/sched/ext/inlines.h b/kernel/sched/ext/inlines.h
index 1e39d12678c4..87b8193785d3 100644
--- a/kernel/sched/ext/inlines.h
+++ b/kernel/sched/ext/inlines.h
@@ -18,9 +18,28 @@ enum scx_dsp_verdict {
SCX_DSP_NONE, /* nothing to run */
SCX_DSP_LOCAL, /* local DSQ has tasks */
SCX_DSP_PREV, /* keep running @prev */
- SCX_DSP_RETRY, /* pick helpers only: restart the pick */
+ SCX_DSP_RETRY, /* restart the pick */
};
+/**
+ * scx_dsp_prev_stale - Test whether dispatch's @prev went stale
+ * @rq: rq being dispatched for
+ * @prev: @rq's donor when dispatch started
+ *
+ * With proxy execution, @prev is the donor and may not be the running task.
+ * Another CPU can reset the donor to rq->curr while dispatch has the rq lock
+ * dropped. Dispatch restarts the pick when that happened and doesn't hand the
+ * old donor to the BPF scheduler.
+ *
+ * During a pick, the donor only ever changes to rq->curr. Only __schedule() on
+ * this CPU sets a different donor, after the pick, so the restarted pick takes
+ * rq->curr as @prev and can't go stale again.
+ */
+static inline bool scx_dsp_prev_stale(struct rq *rq, struct task_struct *prev)
+{
+ return sched_proxy_exec() && unlikely(prev != rq->donor);
+}
+
/*
* One user of this function is scx_bpf_sub_dispatch() which can be called
* recursively as sub-sched dispatches nest. Always inline to reduce stack usage
@@ -33,8 +52,7 @@ scx_dispatch_sched(struct scx_sched *sch, struct rq *rq,
struct scx_dsp_ctx *dspc = &this_cpu_ptr(sch->pcpu)->dsp_ctx;
int nr_loops = SCX_DSP_MAX_LOOPS;
s32 cpu = cpu_of(rq);
- bool prev_on_sch = (prev->sched_class == &ext_sched_class) &&
- scx_task_on_sched(sch, prev);
+ bool prev_on_sch;
if (scx_consume_global_dsq(sch, rq))
return SCX_DSP_LOCAL;
@@ -106,6 +124,11 @@ scx_dispatch_sched(struct scx_sched *sch, struct rq *rq,
rq->scx.sub_dispatch_prev = prev;
#endif
+ /* the dispatch so far may have dropped the rq lock */
+ prev_on_sch = !scx_dsp_prev_stale(rq, prev) &&
+ prev->sched_class == &ext_sched_class &&
+ scx_task_on_sched(sch, prev);
+
SCX_CALL_OP(sch, dispatch, rq, scx_cpu_arg(cpu),
prev_on_sch ? prev : NULL);
@@ -116,7 +139,9 @@ scx_dispatch_sched(struct scx_sched *sch, struct rq *rq,
scx_flush_dispatch_buf(sch, rq);
- if ((prev->scx.flags & SCX_TASK_QUEUED) && prev->scx.slice)
+ /* ops.dispatch() and the flush may have dropped the rq lock */
+ if (!scx_dsp_prev_stale(rq, prev) &&
+ (prev->scx.flags & SCX_TASK_QUEUED) && prev->scx.slice)
return SCX_DSP_PREV;
if (rq->scx.local_dsq.nr)
return SCX_DSP_LOCAL;
--
2.56.0
^ permalink raw reply related [flat|nested] 3+ messages in thread* Re: [PATCH v3 sched_ext/for-7.4-fixes] sched_ext: Fix stale pick when a wakeup resets the donor during dispatch
2026-10-31 1:54 [PATCH v3 sched_ext/for-7.4-fixes] sched_ext: Fix stale pick when a wakeup resets the donor during dispatch Tejun Heo
@ 2026-10-31 2:19 ` sashiko-bot
2026-10-31 7:58 ` Andrea Righi
1 sibling, 0 replies; 3+ messages in thread
From: sashiko-bot @ 2026-10-31 2:19 UTC (permalink / raw)
To: Tejun Heo, sched-ext
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] sched: stale rq->dl_server across RETRY_TASK in __pick_next_task()
--
commit e0269d8eaf30fac4dcf0d1178a69b8f7a54ecfe2
Author: Tejun Heo <tj@kernel.org>
sched_ext: Fix stale pick when a wakeup resets the donor during dispatch
This commit restarts the sched_ext pick when the proxy execution donor passed
as prev to dispatch_one() is reset to rq->curr while the rq lock is dropped,
and avoids passing a stale prev to ops.dispatch() or keeping it afterwards.
> diff --git a/kernel/sched/ext/ext.c b/kernel/sched/ext/ext.c
> index ffaab9fafca87..fe1be3d9444dd 100644
> --- a/kernel/sched/ext/ext.c
> +++ b/kernel/sched/ext/ext.c
> @@ -3407,6 +3407,12 @@ static enum scx_dsp_verdict dispatch_one(struct rq *rq, struct task_struct *prev
> rq->scx.cpu_released = false;
> }
>
> + /* the ecaps sync may have dropped the rq lock */
> + if (scx_dsp_prev_stale(rq, prev)) {
> + verdict = SCX_DSP_RETRY;
> + goto out;
> + }
> +
> if (prev->sched_class == &ext_sched_class) {
> update_curr_scx(rq);
>
> @@ -3449,8 +3455,19 @@ static enum scx_dsp_verdict dispatch_one(struct rq *rq, struct task_struct *prev
> }
>
> verdict = scx_dispatch_sched(root_sch, rq, prev, false);
> - if (verdict != SCX_DSP_NONE)
> +
> + /* scx_dispatch_sched() may have dropped the rq lock */
> + if (scx_dsp_prev_stale(rq, prev))
> + verdict = SCX_DSP_RETRY;
> +
> + switch (verdict) {
> + case SCX_DSP_RETRY:
> + goto out;
[Severity: Medium]
As reported by Andrea Righi on v1 [1], can returning SCX_DSP_RETRY from
dispatch_one() leave a stale rq->dl_server pointer across a pick restart in
__pick_next_task()?
When __pick_next_task() calls pick_task_dl() -> __pick_task_dl() ->
ext_server_pick_task() -> do_pick_task_scx() -> dispatch_pick() ->
dispatch_one(), returning SCX_DSP_RETRY causes do_pick_task_scx() to return
RETRY_TASK even when force_scx is true:
kernel/sched/ext/ext.c:do_pick_task_scx() {
...
if (verdict == SCX_DSP_RETRY) {
p = RETRY_TASK;
goto out;
}
...
}
In __pick_task_dl(), server_pick_task() is only checked for NULL, so
RETRY_TASK causes rq->dl_server to be assigned before returning RETRY_TASK:
kernel/sched/deadline.c:__pick_task_dl() {
...
if (dl_server(dl_se)) {
p = dl_se->server_pick_task(dl_se, rf);
if (!p) {
dl_server_stop(dl_se);
goto again;
}
rq->dl_server = dl_se;
}
...
return p;
}
Unlike pick_task() under CONFIG_SCHED_CORE, __pick_next_task() clears
rq->dl_server before the restart label:
kernel/sched/core.c:__pick_next_task() {
rq->dl_server = NULL;
if (scx_enabled())
goto restart;
...
restart:
prev_balance(rq, rf);
for_each_active_class(class) {
p = class->pick_task(rq, rf);
if (unlikely(p == RETRY_TASK))
goto restart;
if (p) {
put_prev_set_next_task(rq, rq->donor, p);
return p;
}
}
}
If the restarted pass picks a non-server task (for example, if the woken
donor was the only sched_ext task on rq and migrated away so
ext_server_pick_task() returns NULL, or if a stopper or earlier-deadline DL
task is picked), put_prev_set_next_task() -> __put_prev_set_next_dl_server()
will attach the stale rq->dl_server (&rq->ext_server) to next->dl_server on a
non-server task.
Should __pick_next_task() clear rq->dl_server = NULL after the restart label
(or should __pick_task_dl() avoid setting rq->dl_server when server_pick_task
returns RETRY_TASK)?
[1] https://lore.kernel.org/r/auTNPtiaPyO9R5NG@gpd4
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261031015414.219280-1-tj@kernel.org?part=1
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [PATCH v3 sched_ext/for-7.4-fixes] sched_ext: Fix stale pick when a wakeup resets the donor during dispatch
2026-10-31 1:54 [PATCH v3 sched_ext/for-7.4-fixes] sched_ext: Fix stale pick when a wakeup resets the donor during dispatch Tejun Heo
2026-10-31 2:19 ` sashiko-bot
@ 2026-10-31 7:58 ` Andrea Righi
1 sibling, 0 replies; 3+ messages in thread
From: Andrea Righi @ 2026-10-31 7:58 UTC (permalink / raw)
To: Tejun Heo
Cc: sched-ext, David Vernet, Changwoo Min, Emil Tsalapatis, David Dai,
linux-kernel
Hi Tejun,
On Fri, Oct 30, 2026 at 03:54:14PM -1000, Tejun Heo wrote:
> With proxy execution, do_pick_task_scx() passes rq->donor to dispatch_one()
> as @prev. Unlike rq->curr, the donor can be moved to another CPU by a wakeup
> while dispatch_one() has the rq lock dropped:
>
> 1. dispatch_one() drops the rq lock, e.g. to move a task from another CPU.
> 2. Another CPU wakes the donor, which proxy execution migrated to this CPU.
> proxy_needs_return() dequeues it and resets the donor to rq->curr, and
> the wakeup enqueues it, possibly on another CPU.
> 3. dispatch_one() sees @prev queued and returns SCX_DSP_PREV.
> 4. do_pick_task_scx() returns @prev, and this CPU runs a task that is queued
> on another rq.
>
> sched_proxy_block_task() resets the donor the same way when another CPU sets
> @prev's policy to SCHED_EXT or moves it to another BPF scheduler, and blocks
> @prev instead.
>
> Whatever dispatch concluded, and whatever it does with @prev after the drop,
> is about a task this CPU no longer owns. rq_modified_above() catches the
> reset only when rq->curr is in a class above ext, and the dl_server pick
> skips the check.
>
> Restart the pick when @prev is no longer the donor, as dispatch_core_pick()
> already does after a lock drop. dispatch_one() tests after each step that
> can drop the lock, and scx_dispatch_sched() decides per ops.dispatch() call
> whether to hand @prev over, which also covers a class or scheduler change
> across a drop. The donor only ever changes to rq->curr during a pick, so the
> retried pick can't go stale again.
>
> 7a3a6bfbd62a ("sched: Rework prev_balance() to avoid stale prev references")
> closed the same window in prev_balance() by reading rq->donor instead of
> taking @prev. That doesn't work here, as the dispatch never evaluated
> rq->curr, which may not even be a sched_ext task.
>
> Verified with a synthetic reproducer.
>
> v2: Also cover rq lock drops inside dispatch (sashiko).
>
> v3: Don't keep a stale @prev after ops.dispatch() (sashiko).
>
> Fixes: c6fe97c34a1a ("sched: Allow enabling proxy exec with sched_ext")
> Signed-off-by: Tejun Heo <tj@kernel.org>
The dl_server finding reported by Sashiko is valid, but, as you noted,
it's a different core scheduler bug and should be addressed separately.
For this one:
Reviewed-by: Andrea Righi <arighi@nvidia.com>
Thanks,
-Andrea
> ---
> kernel/sched/ext/ext.c | 20 +++++++++++++++++++-
> kernel/sched/ext/inlines.h | 33 +++++++++++++++++++++++++++++----
> 2 files changed, 48 insertions(+), 5 deletions(-)
>
> diff --git a/kernel/sched/ext/ext.c b/kernel/sched/ext/ext.c
> index cd923f9f1f2a..43cf98c1d511 100644
> --- a/kernel/sched/ext/ext.c
> +++ b/kernel/sched/ext/ext.c
> @@ -3407,6 +3407,12 @@ static enum scx_dsp_verdict dispatch_one(struct rq *rq, struct task_struct *prev
> rq->scx.cpu_released = false;
> }
>
> + /* the ecaps sync may have dropped the rq lock */
> + if (scx_dsp_prev_stale(rq, prev)) {
> + verdict = SCX_DSP_RETRY;
> + goto out;
> + }
> +
> if (prev->sched_class == &ext_sched_class) {
> update_curr_scx(rq);
>
> @@ -3449,8 +3455,19 @@ static enum scx_dsp_verdict dispatch_one(struct rq *rq, struct task_struct *prev
> }
>
> verdict = scx_dispatch_sched(root_sch, rq, prev, false);
> - if (verdict != SCX_DSP_NONE)
> +
> + /* scx_dispatch_sched() may have dropped the rq lock */
> + if (scx_dsp_prev_stale(rq, prev))
> + verdict = SCX_DSP_RETRY;
> +
> + switch (verdict) {
> + case SCX_DSP_RETRY:
> + goto out;
> + case SCX_DSP_NONE:
> + break;
> + default:
> goto has_tasks;
> + }
>
> /*
> * Didn't find another task to run. Keep running @prev unless its own
> @@ -3517,6 +3534,7 @@ static enum scx_dsp_verdict dispatch_one(struct rq *rq, struct task_struct *prev
> rq->scx.nr_immed))
> scx_schedule_reenq_local(rq, 0);
>
> +out:
> rq->scx.flags &= ~SCX_RQ_IN_DISPATCH;
> return verdict;
> }
> diff --git a/kernel/sched/ext/inlines.h b/kernel/sched/ext/inlines.h
> index 1e39d12678c4..87b8193785d3 100644
> --- a/kernel/sched/ext/inlines.h
> +++ b/kernel/sched/ext/inlines.h
> @@ -18,9 +18,28 @@ enum scx_dsp_verdict {
> SCX_DSP_NONE, /* nothing to run */
> SCX_DSP_LOCAL, /* local DSQ has tasks */
> SCX_DSP_PREV, /* keep running @prev */
> - SCX_DSP_RETRY, /* pick helpers only: restart the pick */
> + SCX_DSP_RETRY, /* restart the pick */
> };
>
> +/**
> + * scx_dsp_prev_stale - Test whether dispatch's @prev went stale
> + * @rq: rq being dispatched for
> + * @prev: @rq's donor when dispatch started
> + *
> + * With proxy execution, @prev is the donor and may not be the running task.
> + * Another CPU can reset the donor to rq->curr while dispatch has the rq lock
> + * dropped. Dispatch restarts the pick when that happened and doesn't hand the
> + * old donor to the BPF scheduler.
> + *
> + * During a pick, the donor only ever changes to rq->curr. Only __schedule() on
> + * this CPU sets a different donor, after the pick, so the restarted pick takes
> + * rq->curr as @prev and can't go stale again.
> + */
> +static inline bool scx_dsp_prev_stale(struct rq *rq, struct task_struct *prev)
> +{
> + return sched_proxy_exec() && unlikely(prev != rq->donor);
> +}
> +
> /*
> * One user of this function is scx_bpf_sub_dispatch() which can be called
> * recursively as sub-sched dispatches nest. Always inline to reduce stack usage
> @@ -33,8 +52,7 @@ scx_dispatch_sched(struct scx_sched *sch, struct rq *rq,
> struct scx_dsp_ctx *dspc = &this_cpu_ptr(sch->pcpu)->dsp_ctx;
> int nr_loops = SCX_DSP_MAX_LOOPS;
> s32 cpu = cpu_of(rq);
> - bool prev_on_sch = (prev->sched_class == &ext_sched_class) &&
> - scx_task_on_sched(sch, prev);
> + bool prev_on_sch;
>
> if (scx_consume_global_dsq(sch, rq))
> return SCX_DSP_LOCAL;
> @@ -106,6 +124,11 @@ scx_dispatch_sched(struct scx_sched *sch, struct rq *rq,
> rq->scx.sub_dispatch_prev = prev;
> #endif
>
> + /* the dispatch so far may have dropped the rq lock */
> + prev_on_sch = !scx_dsp_prev_stale(rq, prev) &&
> + prev->sched_class == &ext_sched_class &&
> + scx_task_on_sched(sch, prev);
> +
> SCX_CALL_OP(sch, dispatch, rq, scx_cpu_arg(cpu),
> prev_on_sch ? prev : NULL);
>
> @@ -116,7 +139,9 @@ scx_dispatch_sched(struct scx_sched *sch, struct rq *rq,
>
> scx_flush_dispatch_buf(sch, rq);
>
> - if ((prev->scx.flags & SCX_TASK_QUEUED) && prev->scx.slice)
> + /* ops.dispatch() and the flush may have dropped the rq lock */
> + if (!scx_dsp_prev_stale(rq, prev) &&
> + (prev->scx.flags & SCX_TASK_QUEUED) && prev->scx.slice)
> return SCX_DSP_PREV;
> if (rq->scx.local_dsq.nr)
> return SCX_DSP_LOCAL;
> --
> 2.56.0
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-10-31 7:58 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-10-31 1:54 [PATCH v3 sched_ext/for-7.4-fixes] sched_ext: Fix stale pick when a wakeup resets the donor during dispatch Tejun Heo
2026-10-31 2:19 ` sashiko-bot
2026-10-31 7:58 ` Andrea Righi
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.