Re: [PATCHSET sched_ext/for-7.3-fixes] sched_ext: Fix bypass leaving the running task protected and bypassed tasks stranded

[Tejun Heo]

Hello, Andrea.

On Sat, Oct 17, 2026 at 12:12:44PM +0200, Andrea Righi wrote:
>  - when merging for-7.3-fixes into for-7.4, with proxy exec the slice and the
>    protection belong to the donor, so I think the resolution should use rq->donor
>    instead of rq->curr, both for the strip on bypass and for the eviction on
>    unbypass. With rq->curr, a blocked SCX donor would keep its protection into
>    bypass and we'd act on the proxy owner instead.

Yes, the merge into for-7.4 will use rq->donor for both.

>  - not a regression and probably transient (I haven't verified it):
>    bypass_lb_cpu() doesn't look at caps, when the nearest non-bypassing ancestor
>    running a bypassed sched's tasks is itself a sub-sched with caps only on some
>    CPUs, could a bypassed task still be moved to a CPU it can't stay on, until
>    bypass lifts?

Yeah, that's already being worked on in a separate series.

Thanks.

-- 
tejun