From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>,
Emil Tsalapatis <emil@etsalapatis.com>,
David Dai <david.dai@linux.dev>,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [GIT PULL] sched_ext: Fixes for v7.3-rc7
Date: Wed, 14 Oct 2026 12:33:13 -1000 [thread overview]
Message-ID: <3d82bc8d063a217f2d6583d285feca4b@kernel.org> (raw)
Hello,
The following changes since commit e6ac89b8b1c12e9104df45a14a26e2dfa96ded06:
sched_ext: Generate qseq from a per-task counter (2026-10-03 13:23:31 -1000)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git tags/sched_ext-for-7.3-rc7-fixes
for you to fetch changes up to 2935062be77113c1c4565ca9d0c72180449aafee:
sched_ext: Wait for SCX_OPSS_DISPATCHING before moving tasks off DSQs (2026-10-13 09:55:19 -1000)
----------------------------------------------------------------
sched_ext: Fixes for v7.3-rc7
- A task that skipped the BPF scheduler on its way back to its CPU's local
queue could stall there until the watchdog fired, as the CPU had already
decided to go idle.
- Use-after-free of a destroyed user dispatch queue by a deferred re-enqueue
request.
- A task could be moved off a dispatch queue while the dispatching CPU was
still running ops.dequeue() on it.
- Bypass mode mishandled a sub-scheduler bypass overlapping an ancestor's,
as across a system suspend. Descendants could leave bypass mid-teardown
and tasks could be stranded on bypass queues.
- The idle CPU selection helper could return a CPU outside the allowed CPUs
of a pinned or migration-disabled task.
----------------------------------------------------------------
Hui Su (1):
sched_ext: idle: Respect task affinity in restricted CPU selection
Kuba Piecuch (2):
sched_ext: Rename scx_reenq_wait_dispatching() to scx_wait_dispatching()
sched_ext: Wait for SCX_OPSS_DISPATCHING before moving tasks off DSQs
Tejun Heo (4):
sched_ext: Fix stall when a task enqueued with SCX_ENQ_LAST lands back on its CPU's local DSQ
sched_ext: Fix use-after-free of a destroyed user DSQ by a deferred reenqueue
sched_ext: Propagate every bypass depth change to the descendants
sched_ext: Fix the bypass dispatch claim for schedulers bypassed by an ancestor
kernel/sched/ext/ext.c | 123 +++++++++++++++++++++++++++++++-------------
kernel/sched/ext/idle.c | 50 ++++++++++++++----
kernel/sched/ext/internal.h | 7 +--
kernel/sched/ext/sub.c | 2 +-
4 files changed, 132 insertions(+), 50 deletions(-)
--
tejun
reply other threads:[~2026-10-14 22:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3d82bc8d063a217f2d6583d285feca4b@kernel.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=david.dai@linux.dev \
--cc=emil@etsalapatis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=void@manifault.com \
/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.