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>,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [GIT PULL] sched_ext: Fix for v6.19-rc8
Date: Wed, 04 Feb 2026 12:32:41 -1000 [thread overview]
Message-ID: <403d62bc430249eb2904652103e4efa0@kernel.org> (raw)
Hi, Linus.
This is a critical regression fix for a change introduced in this cycle.
The cgroup exit ordering fix (7900aa699c34) which moved sched_ext_free()
to finish_task_switch() created a race window where sched_class operations
could be invoked on dead tasks after sched_ext_dead() already ran, leading
to invalid SCX task state transitions and NULL pointer dereferences.
Thanks.
The following changes since commit c9894e6f0160414b57e895332c580cf5c8da6780:
tools/sched_ext: update scx_show_state.py for scx_aborting change (2025-12-28 06:11:26 -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-6.19-rc8-fixes
for you to fetch changes up to 0eca95cba2b7bf7b7b4f2fa90734a85fcaa72782:
sched_ext: Short-circuit sched_class operations on dead tasks (2026-02-04 12:22:11 -1000)
----------------------------------------------------------------
sched_ext: Fixes for v6.19-rc8
- Fix race where sched_class operations (sched_setscheduler() and friends)
could be invoked on dead tasks after sched_ext_dead() already ran, causing
invalid SCX task state transitions and NULL pointer dereferences. This was
a regression from the cgroup exit ordering fix which moved
sched_ext_free() to finish_task_switch().
----------------------------------------------------------------
Tejun Heo (1):
sched_ext: Short-circuit sched_class operations on dead tasks
kernel/sched/ext.c | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
--
tejun
next reply other threads:[~2026-02-04 22:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 22:32 Tejun Heo [this message]
2026-02-04 23:25 ` [GIT PULL] sched_ext: Fix for v6.19-rc8 pr-tracker-bot
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=403d62bc430249eb2904652103e4efa0@kernel.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--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.