diff options
| author | Tejun Heo <tj@kernel.org> | 2026-07-09 12:06:11 -1000 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2026-07-09 12:06:11 -1000 |
| commit | 31645fb113af646792ebb1e51eceebb9a04fdea1 (patch) | |
| tree | 6397abf23de19cbd27898bc40c9f8623909e0ae5 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | c89b7a09b7a8c5cb5b055a9509a58370abe97b32 (diff) | |
sched_ext: Reject direct slice and dsq_vtime writes for cid-form schedulers
Direct writes to p->scx.slice and p->scx.dsq_vtime bypass
scx_bpf_task_set_slice/dsq_vtime() and the authority checks they carry.
Those checks exist for sub-schedulers, which attach only through the
cid-form struct_ops, so the direct writes only need to be closed there.
Give sched_ext_ops_cid its own verifier ops that reject the two fields.
cid-form is a new interface with no legacy users, so there is no
compatibility to keep. The cpu-form keeps direct writes, and the deprecation
warning they carried is dropped.
Signed-off-by: Tejun Heo <tj@kernel.org>
Reviewed-by: Andrea Righi <arighi@nvidia.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
