Sched_ext development
 help / color / mirror / Atom feed
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-rc4
Date: Fri, 22 May 2026 06:48:26 -1000	[thread overview]
Message-ID: <154badc0cdc979593d4321a2cdb9ef61@kernel.org> (raw)

Hello, Linus.

The following changes since commit 6ae315d37924435516d697ea7dde0b799a5928e0:

  sched_ext: Use HK_TYPE_DOMAIN_BOOT to detect isolcpus= domain isolation (2026-05-13 10:02:57 -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-7.1-rc4-fixes

for you to fetch changes up to 0c1a9dce208b4dc265925898e5da98934f7f9266:

  sched_ext: Fix spurious WARN on stale ops_state in ops_dequeue() (2026-05-21 06:27:44 -1000)

----------------------------------------------------------------
sched_ext: Fixes for v7.1-rc4

- Spurious WARN in ops_dequeue() racing with concurrent dispatch.

- Self-deadlock between scheduler disable and a concurrent sub-sched
  enable.

----------------------------------------------------------------
Samuele Mariotti (1):
      sched_ext: Fix spurious WARN on stale ops_state in ops_dequeue()

Tejun Heo (1):
      sched_ext: Fix deadlock between scx_root_disable() and concurrent forks

 kernel/sched/ext.c | 39 ++++++++++++++++++++++++++++++++++++---
 1 file changed, 36 insertions(+), 3 deletions(-)

Thanks.

--
tejun

             reply	other threads:[~2026-05-22 16:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22 16:48 Tejun Heo [this message]
2026-05-22 23:45 ` [GIT PULL] sched_ext: Fixes for v7.1-rc4 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=154badc0cdc979593d4321a2cdb9ef61@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