From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Koutny <mkoutny@suse.com>,
Waiman Long <longman@redhat.com>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] cgroup: Fixes for v7.4-rc2
Date: Sun, 15 Nov 2026 10:48:42 -1000 [thread overview]
Message-ID: <7a3f079589dddf1444f015b874f1b9ed@kernel.org> (raw)
Hello,
The following changes since commit 518cec2def9992192291f5028edc077fb2e475e9:
cgroup/cpuset: Integrate compute_partition_effective_cpumask() into compute_effective_cpumask() (2026-10-26 07:44:43 -1000)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git tags/cgroup-for-7.4-rc2-fixes
for you to fetch changes up to acec9637e03ca54bd3c3a0c1a6ad5c6dfa07c0df:
cgroup/cpuset: Don't revive invalid partition without active CPU on hotplug (2026-11-15 10:15:12 -1000)
----------------------------------------------------------------
cgroup: Fixes for v7.4-rc2
- A file notification racing the file's removal could re-arm the
notification timer after it was shut down, corrupting the timer wheel or
firing on freed memory.
- The v1 freezer could leave an exiting task frozen forever after its cgroup
was thawed or removed.
- With memcg built without the block cgroup controller, memcg reclaim waited
on writeback and could deadlock against a filesystem freeze. memcg now
selects the controller.
- cpuset partition state could go wrong when CPUs move between nested
partitions or go offline: isolated CPUs leaked or went missing, invalid
partitions kept exclusive CPUs or came back with no usable CPU, and
expanding a remote partition could fail. Separately, a forked child could
inherit a corrupted memory node mask.
----------------------------------------------------------------
Chen Ridong (1):
cpuset: add early empty cpumask check in partition_xcpus_add/del
Christian Brauner (1):
memcg: make MEMCG select BLK_CGROUP
Mani Tofigh (2):
cgroup: arm the notify timer only while the file exists
cgroup/freezer: walk exiting tasks in the v1 freezer
Ridong Chen (5):
cgroup/cpuset: Reset partition data when an invalid partition stays invalid
cpuset: settle isolation state when CPUs are given back to parent
cpuset: generalize the validate_partition() interface
cgroup/cpuset: Remove redundant WARN_ON_ONCE() in remote_cpus_update()
cgroup/cpuset: Don't revive invalid partition without active CPU on hotplug
Tejun Heo (1):
cgroup/freezer: Fix exiting tasks left frozen forever after rmdir
Waiman Long (6):
cgroup/cpuset: Fix incorrect CPU accounting with parent's effective_xcpus expansion
cgroup/cpuset: Recompute effective cpumask in update_cpumasks_hier() after calling update_parent_effective_cpumask()
cgroup/cpuset: Do housekeeping check when isolated child with root parent may get more xcpus
selftests/cgroup: Fix "test_cpuset_prs.sh -v" failures
cgroup/cpuset: Protect current->mems_allowed read in cpuset_fork()
cgroup/cpuset: Correctly set isolated_cpus when switching partition state
init/Kconfig | 1 +
kernel/cgroup/cgroup.c | 22 +-
kernel/cgroup/cpuset.c | 316 +++++++++++-----------
kernel/cgroup/legacy_freezer.c | 40 ++-
tools/testing/selftests/cgroup/test_cpuset_prs.sh | 46 +++-
5 files changed, 251 insertions(+), 174 deletions(-)
--
tejun
reply other threads:[~2026-11-15 20:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=7a3f079589dddf1444f015b874f1b9ed@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