From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Koutny <mkoutny@suse.com>,
Waiman Long <longman@redhat.com>
Subject: [GIT PULL] cgroup: Fixes for v7.3-rc1
Date: Mon, 31 Aug 2026 10:43:14 -1000 [thread overview]
Message-ID: <946c7fbb6329562f80c4900716aaf1a6@kernel.org> (raw)
Hello, Linus.
The following changes since commit 2d19207f3fc8e08bab3270af2e3835358ab1473a:
selftests/cgroup: Remove redundant chown in test_cgcore_lesser_ns_open (2026-08-14 08:32:58 -1000)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git tags/cgroup-for-7.3-rc1-fixes
for you to fetch changes up to 3f4b7d1a49c5c826f3be9b684313eea5b83ac232:
selftests/cgroup: test clone3() into a previously killed cgroup (2026-08-31 06:19:53 -1000)
----------------------------------------------------------------
cgroup: Fixes for v7.3-rc1
- After cgroup.kill was written to a cgroup, every child cloned into it
with CLONE_INTO_CGROUP was spuriously killed because the fork path
snapshotted the kill counter before resolving the target cgroup.
- Releasing an isolated cpuset partition dropped the isolation of CPUs
isolated on the kernel command line.
- Selftest and documentation fixes.
----------------------------------------------------------------
Cheng Lingfei (1):
docs: cgroup-v2: fix misc.events key format description
Etienne Perot (2):
cgroup: fix spurious SIGKILL of CLONE_INTO_CGROUP children
selftests/cgroup: test clone3() into a previously killed cgroup
Guopeng Zhang (3):
selftests/cgroup: Drop invalid boot isolation comparison
cgroup/cpuset: Preserve boot-isolated CPUs on partition release
selftests/cgroup: Add test for preserving boot-isolated CPUs
Hemanth Selam (1):
selftests/cgroup: set the test plan after the setup checks
Hongfu Li (1):
selftests/cgroup: Fix cg_run_in_subcgroups ignoring arg parameter
Documentation/admin-guide/cgroup-v2.rst | 2 +-
include/linux/cgroup-defs.h | 5 +-
kernel/cgroup/cgroup.c | 6 +--
kernel/cgroup/cpuset.c | 39 ++++++++++----
tools/testing/selftests/cgroup/test_core.c | 2 +-
tools/testing/selftests/cgroup/test_cpu.c | 2 +-
tools/testing/selftests/cgroup/test_cpuset.c | 2 +-
tools/testing/selftests/cgroup/test_cpuset_prs.sh | 64 ++++++++++++++++++++---
tools/testing/selftests/cgroup/test_freezer.c | 2 +-
tools/testing/selftests/cgroup/test_kill.c | 57 +++++++++++++++++++-
tools/testing/selftests/cgroup/test_kmem.c | 4 +-
tools/testing/selftests/cgroup/test_memcontrol.c | 2 +-
tools/testing/selftests/cgroup/test_pids.c | 2 +-
tools/testing/selftests/cgroup/test_zswap.c | 2 +-
14 files changed, 159 insertions(+), 32 deletions(-)
Thanks.
--
tejun
next reply other threads:[~2026-08-31 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 20:43 Tejun Heo [this message]
2026-08-31 22:26 ` 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=946c7fbb6329562f80c4900716aaf1a6@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
all inboxes | Powered by JetHome®