From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] cgroup: Changes for v6.17
Date: Wed, 30 Jul 2025 13:09:17 -1000 [thread overview]
Message-ID: <aIqmHVGyKjFG8agb@slm.duckdns.org> (raw)
The following changes since commit 2043ae9019e0f75c7785048230586c3f3ca0a2a4:
Merge tag 'hid-for-linus-2025060301' of git://git.kernel.org/pub/scm/linux/kernel/git/hid/hid (2025-06-03 10:34:36 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git/ tags/cgroup-for-6.17
for you to fetch changes up to 646faf36d7271c597497ca547a59912fcab49be9:
cgroup: Add compatibility option for content of /proc/cgroups (2025-07-19 06:14:44 -1000)
----------------------------------------------------------------
cgroup: Changes for v6.17
- Allow css_rstat_updated() in NMI context to enable memory accounting for
allocations in NMI context.
- /proc/cgroups doesn't contain useful information for cgroup2 and was
updated to only show v1 controllers. This unfortunately broke something in
the wild. Add an option to bring back the old behavior to ease transition.
- selftest updates and other cleanups.
----------------------------------------------------------------
Michal Koutný (6):
cgroup: Drop sock_cgroup_classid() dummy implementation
selftests: cgroup_util: Add helpers for testing named v1 hierarchies
selftests: cgroup: Add support for named v1 hierarchies in test_core
selftests: cgroup: Optionally set up v1 environment
selftests: cgroup: Fix compilation on pre-cgroupns kernels
cgroup: Add compatibility option for content of /proc/cgroups
Sebastian Chlad (2):
selftests: cgroup: Allow longer timeout for kmem_dead_cgroups cleanup
selftests: cgroup: Fix missing newline in test_zswap_writeback_one
Shakeel Butt (5):
cgroup: support to enable nmi-safe css_rstat_updated
cgroup: make css_rstat_updated nmi safe
cgroup: remove per-cpu per-subsystem locks
memcg: cgroup: call css_rstat_updated irrespective of in_nmi()
cgroup: llist: avoid memory tears for llist_node
Shashank Balaji (1):
selftests/cgroup: fix cpu.max tests
Tejun Heo (1):
Merge branch 'for-6.16-fixes' into for-6.17
Vishal Chourasia (1):
Documentation: cgroup: add section explaining controller availability
Documentation/admin-guide/cgroup-v2.rst | 9 +
Documentation/admin-guide/kernel-parameters.txt | 8 +
include/linux/cgroup-defs.h | 21 +--
include/linux/llist.h | 6 +-
include/trace/events/cgroup.h | 47 ------
kernel/cgroup/cgroup-v1.c | 14 +-
kernel/cgroup/rstat.c | 184 ++++++++++-----------
mm/memcontrol.c | 10 +-
tools/testing/selftests/cgroup/lib/cgroup_util.c | 4 +-
.../selftests/cgroup/lib/include/cgroup_util.h | 5 +
tools/testing/selftests/cgroup/test_core.c | 84 ++++++++--
tools/testing/selftests/cgroup/test_cpu.c | 63 ++++---
tools/testing/selftests/cgroup/test_kmem.c | 5 +-
tools/testing/selftests/cgroup/test_zswap.c | 2 +-
14 files changed, 264 insertions(+), 198 deletions(-)
--
tejun
next reply other threads:[~2025-07-30 23:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 23:09 Tejun Heo [this message]
2025-07-31 23:47 ` 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=aIqmHVGyKjFG8agb@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--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®