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>,
linux-kernel@vger.kernel.org, sched-ext@lists.linux.dev
Subject: [GIT PULL] sched_ext: Fixes for v6.16-rc6
Date: Sat, 19 Jul 2025 07:02:54 -1000 [thread overview]
Message-ID: <aHvPvsnPScZVpVAM@slm.duckdns.org> (raw)
The following changes since commit 33796b91871ad4010c8188372dd1faf97cf0f1c0:
sched_ext, sched/core: Don't call scx_group_set_weight() prematurely from sched_create_group() (2025-06-17 08:19:55 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/sched_ext.git/ tags/sched_ext-for-6.16-rc6-fixes
for you to fetch changes up to 06efc9fe0b8deeb83b47fd7c5451fe1a60c8a761:
sched_ext: idle: Handle migration-disabled tasks in idle selection (2025-07-17 08:19:38 -1000)
----------------------------------------------------------------
sched_ext: Fixes for v6.16-rc6
- Fix handling of migration disabled tasks in default idle selection.
- update_locked_rq() called __this_cpu_write() spuriously with NULL when @rq
was not locked. As the writes were spurious, it didn't break anything
directly. However, the function could be called in a preemptible leading
to a context warning in __this_cpu_write(). Skip the spurious NULL writes.
- Selftest fix on UP.
----------------------------------------------------------------
Andrea Righi (2):
selftests/sched_ext: Fix exit selftest hang on UP
sched_ext: idle: Handle migration-disabled tasks in idle selection
Breno Leitao (1):
sched/ext: Prevent update_locked_rq() calls with NULL rq
kernel/sched/ext.c | 12 ++++++++----
kernel/sched/ext_idle.c | 2 +-
tools/testing/selftests/sched_ext/exit.c | 8 ++++++++
3 files changed, 17 insertions(+), 5 deletions(-)
--
tejun
next reply other threads:[~2025-07-19 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-19 17:02 Tejun Heo [this message]
2025-07-19 18:29 ` 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=aHvPvsnPScZVpVAM@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.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
all inboxes | Powered by JetHome®