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 Koutný" <mkoutny@suse.com>,
"Waiman Long" <longman@redhat.com>
Subject: [GIT PULL] cgroup: Fixes for v7.1-rc2
Date: Tue, 05 May 2026 12:05:39 -1000 [thread overview]
Message-ID: <f5258b93b0a513c90b4129177a2eb50d@kernel.org> (raw)
Hello,
The following changes since commit 981cd338614c96070cf9854679014fd027c1fb1d:
docs: cgroup: fix typo 'protetion' -> 'protection' (2026-04-27 07:55:40 -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-rc2-fixes
for you to fetch changes up to d8769544bde51b0ac980d10f8fe9f9fed6c95995:
docs: cgroup-v1: Update charge-commit section (2026-05-04 11:02:12 -1000)
----------------------------------------------------------------
cgroup: Fixes for v7.1-rc2
- During v6.19, cgroup task unlink was moved from do_exit() to after the
final task switch to satisfy a controller invariant. That left the kernel
seeing tasks past exit_signals() longer than userspace expected, and
several v7.0 follow-ups tried to bridge the gap by making rmdir wait for
the kernel side. None held up. The latest is an A-A deadlock when rmdir
is invoked by the reaper of zombies whose pidns teardown the rmdir itself
is waiting on, which points at the synchronizing approach being
fundamentally wrong:
- Take a different approach: drop the wait, leave rmdir's user-visible
side returning as soon as cgroup.procs is empty, and defer the css
percpu_ref kill that drives ->css_offline() until the cgroup is fully
depopulated.
- Tagged for stable. Somewhat invasive but contained. The hope is that
fixing forward sticks. If not, the fallback is to revert the entire
chain and rework on the development branch.
- Doesn't plug a pre-existing analogous race in
cgroup_apply_control_disable() (controller disable via subtree_control).
Not a regression. The development branch will do the more invasive
restructuring needed for that.
- Documentation update for cgroup-v1 charge-commit section that still
referenced functions removed when the memcg hugetlb try-commit-cancel
protocol was retired.
----------------------------------------------------------------
T.J. Mercier (1):
docs: cgroup-v1: Update charge-commit section
Tejun Heo (1):
cgroup: Defer css percpu_ref kill on rmdir until cgroup is depopulated
Documentation/admin-guide/cgroup-v1/memcg_test.rst | 6 +-
include/linux/cgroup-defs.h | 4 +-
kernel/cgroup/cgroup.c | 250 ++++++++++-----------
3 files changed, 121 insertions(+), 139 deletions(-)
Thanks.
--
tejun
next reply other threads:[~2026-05-05 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 22:05 Tejun Heo [this message]
2026-05-05 23:55 ` [GIT PULL] cgroup: Fixes for v7.1-rc2 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=f5258b93b0a513c90b4129177a2eb50d@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