diff options
| author | Tejun Heo <tj@kernel.org> | 2026-05-10 12:51:09 -1000 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2026-05-10 12:51:09 -1000 |
| commit | b5646c627652241f248f0a4ff31b1d32316b0068 (patch) | |
| tree | fb4c2b67c5ad7662894a77fa1ca540b7716fdd25 /include/linux/timerqueue.h | |
| parent | f25ad1e3cbaa4c87bb2b11496786f79db54c294f (diff) | |
| parent | d3e73a0808ddfb91ac36cd548643cbbeb00ad4db (diff) | |
Merge branch 'for-7.1-fixes' into for-7.2
Conflict between:
[1] 41e3312861ea ("sched_ext: add p->scx.tid and SCX_OPS_TID_TO_TASK lookup")
[2] c941d7391f25 ("sched_ext: Close root-enable vs sched_ext_dead() race with SCX_TASK_INIT_BEGIN")
in scx_root_enable_workfn()'s post-init block. [1] added a tid hash
insertion under a scoped_guard() for scx_tasks_lock; [2] wraps the same
region in task_rq_lock() for a DEAD recheck. A naive merge would invert the
iter's outer/inner order.
[3] f25ad1e3cbaa ("sched_ext: Add scx_task_iter_relock() and use it in scx_root_enable_workfn()")
was added to for-7.2 for a clean resolution: scx_task_iter_relock(iter, p)
takes both scx_tasks_lock and @p's rq lock in iter order.
Resolved by routing both sides through [3]'s dual-lock helper: the post-init
region runs under a single scx_task_iter_relock() acquisition, with [2]'s
state machine and [1]'s hash insert in sequence inside it.
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'include/linux/timerqueue.h')
0 files changed, 0 insertions, 0 deletions
