From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
cgroups@vger.kernel.org
Subject: [GIT PULL] cgroup: Fixes for v6.17-rc6
Date: Wed, 17 Sep 2025 09:19:48 -1000 [thread overview]
Message-ID: <aMsJ1J994GFBkKt7@slm.duckdns.org> (raw)
The following changes since commit 6563623e604e3e235b2cee71190a4972be8f986b:
docs: cgroup: fixed spelling mistakes in documentation (2025-08-12 10:52:28 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git/ tags/cgroup-for-6.17-rc6-fixes
for you to fetch changes up to 94a4acfec14615e971eb2c9e1fa6c992c85ff6c6:
cgroup/psi: Set of->priv to NULL upon file release (2025-08-22 07:47:43 -1000)
----------------------------------------------------------------
cgroup: Fixes for v6.17-rc6
This contains two cgroup changes. Both are pretty low risk.
- Fix deadlock in cgroup destruction when repeatedly mounting/unmounting
perf_event and net_prio controllers. The issue occurs because
cgroup_destroy_wq has max_active=1, causing root destruction to wait for
CSS offline operations that are queued behind it. The fix splits
cgroup_destroy_wq into three separate workqueues to eliminate the
blocking.
- Set of->priv to NULL upon file release to make potential bugs to manifest
as NULL pointer dereferences rather than use-after-free errors.
----------------------------------------------------------------
Chen Ridong (2):
cgroup: split cgroup_destroy_wq into 3 workqueues
cgroup/psi: Set of->priv to NULL upon file release
kernel/cgroup/cgroup.c | 44 +++++++++++++++++++++++++++++++++++++-------
1 file changed, 37 insertions(+), 7 deletions(-)
--
tejun
next reply other threads:[~2025-09-17 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 19:19 Tejun Heo [this message]
2025-09-17 20:32 ` 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=aMsJ1J994GFBkKt7@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®