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: Fixes for v7.1-rc6
Date: Tue, 02 Jun 2026 12:47:38 -1000 [thread overview]
Message-ID: <eaed7efc3d9465b3986fd1ce89d7257a@kernel.org> (raw)
Hello,
Two low-risk fixes, both contained within sched_ext.
The following changes since commit 0c1a9dce208b4dc265925898e5da98934f7f9266:
sched_ext: Fix spurious WARN on stale ops_state in ops_dequeue() (2026-05-21 06:27:44 -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.1-rc6-fixes
for you to fetch changes up to 02e545c4297a26dbbc41df81b831e7f605bcd306:
sched_ext: Don't warn on NULL cgrp_moving_from in scx_cgroup_move_task() (2026-06-02 11:27:50 -1000)
----------------------------------------------------------------
sched_ext: Fixes for v7.1-rc6
Two low-risk fixes:
- Drop a spurious warning that can fire during cgroup migration while a
sched_ext scheduler is loaded.
- Fix a drgn-based debug script that broke after scheduler state moved into
a per-scheduler struct.
----------------------------------------------------------------
Tejun Heo (1):
sched_ext: Don't warn on NULL cgrp_moving_from in scx_cgroup_move_task()
Zicheng Qu (1):
tools/sched_ext: Fix scx_show_state per-scheduler state reads
kernel/sched/ext.c | 10 ++++++----
tools/sched_ext/scx_show_state.py | 19 +++++++++++++------
2 files changed, 19 insertions(+), 10 deletions(-)
--
tejun
next reply other threads:[~2026-06-02 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 22:47 Tejun Heo [this message]
2026-06-04 19:31 ` [GIT PULL] sched_ext: Fixes for v7.1-rc6 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=eaed7efc3d9465b3986fd1ce89d7257a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox