In the Linux kernel, the following vulnerability has been resolved:<\/p>\n
sched_ext: Fix rq->core_pick corruption under core scheduling<\/p>\n
Core scheduling’s pick_next_task() picks what to run on every SMT sibling of
\nthe core in a single pass under the shared core-wide rq lock. The selection
\nstate is consistent only while the lock is held continuously, so
\n->pick_task() originally could not release it. However, since 4c95380701f5
\n(“sched\/ext: Fold balance_scx() into pick_task_scx()”), sched_ext runs
\ndispatch from inside the pick and dispatching can drop the rq lock. To
\nsupport this, pick_next_task() has been updated to restart the whole
\nselection when a pick returns RETRY_TASK after releasing the lock.<\/p>\n
When selections on the same core interleave through the dropped lock, they
\ncorrupt each other’s state: one clears the other’s rq->core_pick leading to
\na NULL deref, or invalidates its keep-the-previous-task decision leaving a
\ndequeued task running, which deadlocks the next wakeup and matches the
\nreported hard hangs. A cookied ping-pong load on an SMT machine makes the
\ninterleavings frequent and kills the kernel within seconds.<\/p>\n
Fix it by making the pick return RETRY_TASK whenever dispatch released the
\nrq lock, so that a selection only ever commits picks made under a
\ncontinuously held lock. The previous patch’s rq->scx.lock_drop_seq counts
\nthe releases. A dispatch that touched nothing never releases the lock and
\nits verdict, including “nothing to run”, stands: retries are bounded, each
\nfollowing a dispatch that actually did something, and an idle CPU does not
\nloop.<\/p>\n
If another dispatch is already in flight on the rq, skip dispatching and
\npick from what is already queued locally – the in-flight dispatch has
\nreleased the lock, so its own selection will retry and re-pick this rq,
\nwhile returning RETRY_TASK here would only spin on the lock that dispatch
\nneeds to finish.<\/p>\n
Balance callbacks must run in the context that queued them, so they can only
\nbe queued on the CPU’s own rq. When dispatching for another rq, run the
\ndeferred work directly instead – that rq may consume all its picks through
\nthe core-sched fast path and never queue the callback itself.<\/p>\n
The put_prev_task_scx() warning about a runnable task being left behind
\nassumed that dispatch ran as part of the very pick that is switching away.
\nThat now only holds on the non-core path, so gate it and drop the
\ncookie-match test, which is always true without core scheduling, from its
\ncondition.<\/p>\n","protected":false},"excerpt":{"rendered":"
In the Linux kernel, the following vulnerability has been resolved:<\/p>\n
sched_ext: Fix rq->core_pick corruption under core scheduling<\/p>\n
Core scheduling’s pick_next_task() picks what to run on every SMT si<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-21439","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/21439","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=21439"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=21439"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=21439"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}