The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	Michal Koutný <mkoutny@suse.com>,
	Waiman Long <longman@redhat.com>,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] cgroup: Fixes for v7.1-rc3
Date: Wed, 13 May 2026 10:59:45 -1000	[thread overview]
Message-ID: <6038eeed9424f26cc6bec8c0a01c8e43@kernel.org> (raw)

Hello, Linus.

The following changes since commit d8769544bde51b0ac980d10f8fe9f9fed6c95995:

  docs: cgroup-v1: Update charge-commit section (2026-05-04 11:02:12 -1000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git tags/cgroup-for-7.1-rc3-fixes

for you to fetch changes up to 345f40166694e60db6d5cf02233814bb27ac5dec:

  cgroup/cpuset: Return only actually allocated CPUs during partition invalidation (2026-05-13 08:54:53 -1000)

----------------------------------------------------------------
cgroup: Fixes for v7.1-rc3

- cpuset fixes:
  - Partition invalidation could return CPUs still in use by sibling
    partitions, producing overlapping effective_cpus.
  - cpuset_can_attach() over-reserved DL bandwidth on moves that stayed
    within the same root domain.
  - Pending DL migration state leaked into later attaches when a later
    can_attach() check failed.
  - Reorder PF_EXITING and __GFP_HARDWALL checks so dying tasks can
    allocate from any node and exit quickly.

- dmem: propagate -ENOMEM instead of spinning forever when the fallback
  pool allocation also fails.

- selftests/cgroup: percpu test error-path leak, bogus numeric
  comparison of cpuset strings, and a zero-length read() that silently
  passed OOM-kill tests.

----------------------------------------------------------------
Chen Wandun (1):
      cgroup/cpuset: move PF_EXITING check before __GFP_HARDWALL in cpuset_current_node_allowed()

Guopeng Zhang (3):
      cgroup/dmem: Return -ENOMEM on failed pool preallocation
      cgroup/cpuset: Reset DL migration state on can_attach() failure
      cgroup/cpuset: Reserve DL bandwidth only for root-domain moves

Hongfu Li (2):
      selftests/cgroup: Fix cg_read_strcmp() empty string comparison
      selftests/cgroup: Fix string comparison in write_test

Yu Miao (1):
      selftests/cgroup: Fix error path leaks in test_percpu_basic

sunshaojie (1):
      cgroup/cpuset: Return only actually allocated CPUs during partition invalidation

 include/linux/sched/deadline.h                     |  9 ++++
 kernel/cgroup/cpuset-internal.h                    |  1 +
 kernel/cgroup/cpuset.c                             | 56 ++++++++++++----------
 kernel/cgroup/dmem.c                               |  1 +
 kernel/sched/deadline.c                            | 13 +++--
 tools/testing/selftests/cgroup/lib/cgroup_util.c   |  5 +-
 .../selftests/cgroup/test_cpuset_v1_base.sh        |  2 +-
 tools/testing/selftests/cgroup/test_kmem.c         | 10 ++--
 8 files changed, 63 insertions(+), 34 deletions(-)

Thanks.

--
tejun

             reply	other threads:[~2026-05-13 20:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13 20:59 Tejun Heo [this message]
2026-05-14 16:40 ` [GIT PULL] cgroup: Fixes for v7.1-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=6038eeed9424f26cc6bec8c0a01c8e43@kernel.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mkoutny@suse.com \
    --cc=torvalds@linux-foundation.org \
    /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