public inbox for sched-ext@lists.linux.dev
 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.0-rc3
Date: Fri, 13 Mar 2026 10:28:37 -1000	[thread overview]
Message-ID: <00374b06f5f22a6c7af1edd5652bcc60@kernel.org> (raw)

Hello,

The following changes since commit 0031c06807cfa8aa51a759ff8aa09e1aa48149af:

  Merge tag 'cgroup-for-7.0-rc2-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup (2026-03-03 14:25:18 -0800)

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.0-rc3-fixes

for you to fetch changes up to 2fcfe5951eb2e8440fc5e1dd6ea977336ff83a1d:

  sched_ext: Use WRITE_ONCE() for the write side of scx_enable helper pointer (2026-03-09 06:08:26 -1000)

----------------------------------------------------------------
sched_ext: Fixes for v7.0-rc3

- Fix data races flagged by KCSAN: add missing READ_ONCE()/WRITE_ONCE()
  annotations for lock-free accesses to module parameters and dsq->seq.

- Fix silent truncation of upper 32 enqueue flags (SCX_ENQ_PREEMPT and
  above) when passed through the int sched_class interface.

- Documentation updates: scheduling class precedence, task ownership
  state machine, example scheduler descriptions, config list cleanup.

- Selftest fix for format specifier and buffer length in
  file_write_long().

----------------------------------------------------------------
Andrea Righi (1):
      sched_ext: Document task ownership state machine

Cheng-Yang Chou (2):
      sched_ext/selftests: Fix format specifier and buffer length in file_write_long()
      sched_ext: Documentation: Update sched-ext.rst

Christian Loehle (1):
      sched_ext: Documentation: Mention scheduling class precedence

David Carlier (1):
      sched_ext: Use READ_ONCE() for scx_slice_bypass_us in scx_bypass()

Tejun Heo (1):
      sched_ext: Fix enqueue_task_scx() truncation of upper enqueue flags

zhidao su (3):
      sched_ext: Use WRITE_ONCE() for the write side of dsq->seq update
      sched_ext: Use READ_ONCE() for lock-free reads of module param variables
      sched_ext: Use WRITE_ONCE() for the write side of scx_enable helper pointer

 Documentation/scheduler/sched-ext.rst    |  30 +++++++-
 kernel/sched/ext.c                       |  22 +++---
 kernel/sched/ext_internal.h              | 114 ++++++++++++++++++++++++++-----
 tools/testing/selftests/sched_ext/util.c |   4 +-
 4 files changed, 138 insertions(+), 32 deletions(-)

Thanks.

--
tejun

             reply	other threads:[~2026-03-13 20:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13 20:28 Tejun Heo [this message]
2026-03-13 22:15 ` [GIT PULL] sched_ext: Fixes for v7.0-rc3 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=00374b06f5f22a6c7af1edd5652bcc60@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