From: sashiko-bot@kernel.org
To: "Tejun Heo" <tj@kernel.org>
Cc: sched-ext@lists.linux.dev
Subject: Re: [PATCH v2 sched_ext/for-7.3 27/36] sched_ext: Route task slice writes through set_task_slice()
Date: Mon, 06 Jul 2026 02:05:03 +0000 [thread overview]
Message-ID: <20260706020505.9B8FD1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260706014058.439853-28-tj@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Routing the lazy fallback assignment through set_task_slice() in scx_bpf_dsq_insert___v2() and scx_dsq_insert_vtime() incorrectly drops pending out-of-band slice requests when preserving the current slice.
--
commit 127371a444f95f70296cadcc3202bbe1233bead6
Author: Tejun Heo <tj@kernel.org>
sched_ext: Route task slice writes through set_task_slice()
This commit introduces set_task_slice() to centralize writes to p->scx.slice.
It replaces direct assignments across the sched_ext code in preparation for
dropping pending out-of-band slice requests on slice writes.
> diff --git a/kernel/sched/ext/ext.c b/kernel/sched/ext/ext.c
> index 9fa4cfbc75c84..ff997ba881b02 100644
> --- a/kernel/sched/ext/ext.c
> +++ b/kernel/sched/ext/ext.c
[ ... ]
> @@ -8021,9 +8027,9 @@ __bpf_kfunc bool scx_bpf_dsq_insert___v2(struct task_struct *p, u64 dsq_id,
> return false;
>
> if (slice)
> - p->scx.slice = slice;
> + set_task_slice(p, slice);
> else
> - p->scx.slice = p->scx.slice ?: 1;
> + set_task_slice(p, p->scx.slice ?: 1);
[Severity: High]
Will this unconditional call to set_task_slice() accidentally drop pending
out-of-band requests when slice == 0 and p->scx.slice is already non-zero?
The commit message mentions that a later change will make every write
through set_task_slice() drop pending out-of-band slice requests. If a BPF
scheduler passes slice == 0 to scx_bpf_dsq_insert___v2() intending to
preserve the current slice, routing this fallback through set_task_slice()
performs an explicit in-band write of the old slice.
Could this cause the task to lose its assigned slice budget from an
out-of-band request (e.g. set via scx_bpf_task_set_slice()), reverting to
its old slice or a 1ns slice and potentially causing starvation?
Should this avoid calling set_task_slice() if p->scx.slice is already
non-zero? For example: else if (!p->scx.slice) set_task_slice(p, 1);
>
> scx_dsq_insert_commit(sch, p, dsq_id, enq_flags);
>
> @@ -8047,9 +8053,9 @@ static bool scx_dsq_insert_vtime(struct scx_sched *sch, struct task_struct *p,
> return false;
>
> if (slice)
> - p->scx.slice = slice;
> + set_task_slice(p, slice);
> else
> - p->scx.slice = p->scx.slice ?: 1;
> + set_task_slice(p, p->scx.slice ?: 1);
[Severity: High]
Similarly for scx_dsq_insert_vtime(), does unconditional use of
set_task_slice() here clear the pending out-of-band request when preserving
the existing slice?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260706014058.439853-1-tj@kernel.org?part=27
next prev parent reply other threads:[~2026-07-06 2:05 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 1:40 [PATCHSET v2 sched_ext/for-7.3] sched_ext: Capability-based CPU delegation for sub-schedulers Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 01/36] sched_ext: Add SCX_CALL_CID_OP_TASK() for cid-form op dispatch Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 02/36] sched_ext: Rename extra_enq_flags to remote_activate_enq_flags Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 03/36] sched_ext: Fix premature ops->priv publication in scx_alloc_and_add_sched() Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 04/36] tools/sched_ext: scx - Fix cmask_subset(), cmask_equal() and cmask_weight() Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 05/36] sched_ext: Use READ_ONCE/WRITE_ONCE in cmask word ops and drop _RACY variants Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 06/36] tools/sched_ext: scx_qmap - Use bare u64/u32/s32 integer types Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 07/36] sched_ext: Reject direct slice and dsq_vtime writes for cid-form schedulers Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 08/36] sched_ext: Make scx_bpf_kick_cid() return void Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 09/36] sched_ext: Make the kick machinery per-sched Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 10/36] sched_ext: Add ops.init_cids() to finalize the cid layout before init Tejun Heo
2026-07-06 2:08 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 11/36] sched_ext: Add CID sharding Tejun Heo
2026-07-06 1:53 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 12/36] sched_ext: Add shard boundaries to scx_bpf_cid_override() Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 13/36] sched_ext: Defer scx_sched kobj sysfs add into the enable workfns Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 14/36] sched_ext: Add per-shard scx_sched storage scaffolding Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 15/36] sched_ext: Add scx_cmask_ref for validated arena cmask access Tejun Heo
2026-07-06 1:58 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 9:04 ` Andrea Righi
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 16/36] sched_ext: Build the set_cmask scratch from trusted geometry Tejun Heo
2026-07-06 1:59 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 17/36] sched_ext: RCU-protect the sub-sched tree's children/sibling lists Tejun Heo
2026-07-06 2:08 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 18/36] sched_ext: Add scx_skip_subtree_pre() Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 19/36] sched_ext: Add per-shard cap delegation for sub-schedulers Tejun Heo
2026-07-06 2:13 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 20/36] sched_ext: Add coalescing sub_caps_updated() notifier " Tejun Heo
2026-07-06 2:06 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 21/36] sched_ext: Maintain per-cpu effective cap copies for single-read checks Tejun Heo
2026-07-06 2:07 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 22/36] sched_ext: Add sub_ecaps_updated() effective-cap change notifier Tejun Heo
2026-07-06 2:09 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 23/36] sched_ext: Generalize local-DSQ handling to rq-owned DSQs Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 24/36] sched_ext: Add reject DSQ for cap-rejected dispatches Tejun Heo
2026-07-06 2:08 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 25/36] sched_ext: Add the SCX_CAP_ENQ_IMMED cap Tejun Heo
2026-07-06 2:10 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 26/36] sched_ext: Assign a unique id to each scheduler instance Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 27/36] sched_ext: Route task slice writes through set_task_slice() Tejun Heo
2026-07-06 2:05 ` sashiko-bot [this message]
2026-07-06 23:40 ` Tejun Heo
2026-07-06 9:10 ` Andrea Righi
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 28/36] sched_ext: Tie cpu occupancy to SCX_CAP_BASE through the task slice Tejun Heo
2026-07-06 2:07 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 29/36] sched_ext: Add the SCX_CAP_ENQ cap Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 30/36] sched_ext: Gate kicks on SCX_CAP_BASE and preemption on SCX_CAP_PREEMPT Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 31/36] sched_ext: Authorize remote-move inserts against the placing scheduler Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 32/36] sched_ext: Route ops.update_idle() to sub-schedulers and re-notify owed scheds Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 33/36] sched_ext: Replay ecaps notifications suppressed by bypass Tejun Heo
2026-07-06 2:11 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 34/36] sched_ext: Add scx_bpf_sub_kill() to evict a child sub-scheduler Tejun Heo
2026-07-06 2:12 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 35/36] tools/sched_ext: scx_qmap - Expand hierarchical sub-scheduling Tejun Heo
2026-07-06 2:10 ` sashiko-bot
2026-07-06 23:40 ` Tejun Heo
2026-07-06 1:40 ` [PATCH v2 sched_ext/for-7.3 36/36] tools/sched_ext: scx_qmap - Add sub-sched cap fault injection 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=20260706020505.9B8FD1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
/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