From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org
Subject: [GIT PULL] cgroup: Fixes for v6.4-rc7
Date: Wed, 21 Jun 2023 12:05:53 -1000 [thread overview]
Message-ID: <ZJN0Qa--_aBSJ_K3@slm.duckdns.org> (raw)
The following changes since commit 5647e53f7856bb39dae781fe26aa65a699e2fc9f:
cgroup: Documentation: Clarify usage of memory limits (2023-06-05 14:08:12 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git/ cgroup-for-6.4-rc7-fixes
for you to fetch changes up to 6f363f5aa845561f7ea496d8b1175e3204470486:
cgroup: Do not corrupt task iteration when rebinding subsystem (2023-06-12 07:21:57 -1000)
----------------------------------------------------------------
cgroup: Fixes for v6.4-rc7
It's late but here are two bug fixes. Both fix problems which can be severe
but are very confined in scope. The risk to most use cases should be
minimal.
* Fix for an old bug which triggers if a cgroup subsystem is remounted to a
different hierarchy while someone is reading its cgroup.procs/tasks file.
The risk is pretty low given how seldom cgroup subsystems are moved across
hierarchies.
* We moved cpus_read_lock() outside of cgroup internal locks a while ago but
forgot to update the legacy_freezer leading to lockdep triggers. Fixed.
----------------------------------------------------------------
Tetsuo Handa (1):
cgroup,freezer: hold cpu_hotplug_lock before freezer_mutex in freezer_css_{online,offline}()
Xiu Jianfeng (1):
cgroup: Do not corrupt task iteration when rebinding subsystem
kernel/cgroup/cgroup.c | 20 +++++++++++++++++---
kernel/cgroup/legacy_freezer.c | 8 ++++++--
2 files changed, 23 insertions(+), 5 deletions(-)
--
tejun
next reply other threads:[~2023-06-21 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 22:05 Tejun Heo [this message]
2023-06-23 1:03 ` 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=ZJN0Qa--_aBSJ_K3@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®