From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Chen Ridong <chenridong@huawei.com>,
Maarten Lankhorst <dev@lankhorst.se>,
Maxime Ripard <mripard@kernel.org>,
Natalie Vock <natalie.vock@gmx.de>,
Waiman Long <longman@redhat.com>,
cgroups@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] cgroup fixes for v6.19-rc8
Date: Mon, 02 Feb 2026 11:12:59 -1000 [thread overview]
Message-ID: <2fe2b534479363ab3aad3db25fa65377@kernel.org> (raw)
Hi Linus,
Three dmem fixes. While it's late in the cycle, all changes are confined to
kernel/cgroup/dmem.c and can only affect dmem controller users.
Thanks.
The following changes since commit 84697bf5532923f70ac99ea9784fab325c560df0:
kernel: cgroup: Add LGPL-2.1 SPDX license ID to legacy_freezer.c (2026-01-15 22:03:15 -1000)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git tags/cgroup-for-6.19-rc8-fixes
for you to fetch changes up to 99a2ef500906138ba58093b9893972a5c303c734:
cgroup/dmem: avoid pool UAF (2026-02-02 06:04:13 -1000)
----------------------------------------------------------------
cgroup: Fixes for v6.19-rc8
Three dmem fixes from Chen Ridong addressing use-after-free, RCU warning,
and NULL pointer dereference issues introduced with the dmem controller.
All changes are confined to kernel/cgroup/dmem.c and can only affect dmem
controller users.
----------------------------------------------------------------
Chen Ridong (3):
cgroup/dmem: fix NULL pointer dereference when setting max
cgroup/dmem: avoid rcu warning when unregister region
cgroup/dmem: avoid pool UAF
kernel/cgroup/dmem.c | 70 ++++++++++++++++++++++++++++++++++++++++++++++------
1 file changed, 63 insertions(+), 7 deletions(-)
--
tejun
next reply other threads:[~2026-02-02 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 21:12 Tejun Heo [this message]
2026-02-03 1:19 ` [GIT PULL] cgroup fixes for v6.19-rc8 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=2fe2b534479363ab3aad3db25fa65377@kernel.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=dev@lankhorst.se \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mripard@kernel.org \
--cc=natalie.vock@gmx.de \
--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