From: Tejun Heo <tj@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: sched-ext@lists.linux.dev
Subject: Re: [PATCH 12/12] sched_ext: scx_qmap - Add rescue support
Date: Sun, 02 Aug 2026 09:51:45 -1000 [thread overview]
Message-ID: <53990ac674de2b3dfcec0fb18168a5ab@kernel.org> (raw)
In-Reply-To: <20260801090603.593D51F00AC4@smtp.kernel.org>
On Sat, Aug 01, 2026 at 09:06:02AM +0000, sashiko-bot@kernel.org wrote:
> [Severity: High]
> Does removing the !(enq_flags & SCX_ENQ_REENQ) check here cause an
> infinite bounce loop when rescue is disabled kernel-side?
>
> If scx_qmap is executed with -B 0, the kernel capability check rejects the
> insert and bounces the task back to ops.enqueue() with the SCX_ENQ_REENQ
> flag.
>
> Without the check for SCX_ENQ_REENQ, qmap_enqueue() will immediately hit
> this condition again and force-insert the task back to the target CPU.
>
> Could this lead to an endless, unthrottled loop that locks up the core?
The loop is bounded. Each bounce goes back through scx_do_enqueue_task()
which counts it in p->scx.reenq_cnt, and crossing SCX_REENQ_MAX_REPEAT
ejects the owning scheduler. With -B 0, a stranded task takes down qmap
instead of starving or burning the CPU, which is the intended failure mode
when rescue is turned off.
Thanks.
--
tejun
next prev parent reply other threads:[~2026-08-02 19:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 8:51 [PATCHSET sched_ext/for-7.3] sched_ext: Bandwidth-limited rescue execution for stranded tasks Tejun Heo
2026-08-01 8:51 ` [PATCH 01/12] sched_ext: Rename scx_local_or_reject_dsq() to scx_resolve_local_dsq() Tejun Heo
2026-08-01 8:51 ` [PATCH 02/12] sched_ext: Make several ext.c helpers available outside ext.c Tejun Heo
2026-08-01 8:58 ` sashiko-bot
2026-08-01 8:51 ` [PATCH 03/12] sched_ext: Factor out __scx_bpf_now() Tejun Heo
2026-08-01 8:51 ` [PATCH 04/12] sched_ext: Reject internal enq_flags in the dsq move kfuncs Tejun Heo
2026-08-01 8:51 ` [PATCH 05/12] sched_ext: Make SCX_ENQ_IGNORE_CAPS waive the preemption cap too Tejun Heo
2026-08-01 8:51 ` [PATCH 06/12] sched_ext: Synchronize slice and dsq_vtime writes Tejun Heo
2026-08-01 8:51 ` [PATCH 07/12] sched_ext: Add SCX_TASK_PROTECTED Tejun Heo
2026-08-01 8:51 ` [PATCH 08/12] sched_ext: Add bandwidth-limited rescue execution for stranded tasks Tejun Heo
2026-08-01 8:51 ` [PATCH 09/12] sched_ext: Eject the top rescue consumer on overload Tejun Heo
2026-08-01 9:11 ` sashiko-bot
2026-08-01 8:51 ` [PATCH 10/12] sched_ext: Sync tools autogen enum headers Tejun Heo
2026-08-01 8:51 ` [PATCH 11/12] sched_ext: scx_qmap - Idle-check pinned tasks before direct dispatch Tejun Heo
2026-08-01 9:06 ` sashiko-bot
2026-08-01 8:51 ` [PATCH 12/12] sched_ext: scx_qmap - Add rescue support Tejun Heo
2026-08-01 9:06 ` sashiko-bot
2026-08-02 19:51 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-02 21:54 [PATCHSET v2 sched_ext/for-7.3] sched_ext: Bandwidth-limited rescue execution for stranded tasks Tejun Heo
2026-08-02 21:54 ` [PATCH 12/12] sched_ext: scx_qmap - Add rescue support 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=53990ac674de2b3dfcec0fb18168a5ab@kernel.org \
--to=tj@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sched-ext@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.