From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
Waiman Long <longman@redhat.com>
Subject: [GIT PULL] cgroup fixes for v5.17-rc2
Date: Thu, 3 Feb 2022 06:13:32 -1000 [thread overview]
Message-ID: <Yfv/LMxqHSa3s5YS@slm.duckdns.org> (raw)
Hello, Linus.
cgroup fixes for v5.17-rc2 including:
* Eric's fix for a long standing cgroup1 permission issue where it only
checks for uid 0 instead of CAP which inadvertently allows unprivileged
userns roots to modify release_agent userhelper.
* Fixes for the fallouts from Waiman's recent cpuset work.
Thanks.
The following changes since commit daadb3bd0e8d3e317e36bc2c1542e86c528665e5:
Merge tag 'locking_core_for_v5.17_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2022-01-11 17:24:45 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-5.17-fixes
for you to fetch changes up to 2bdfd2825c9662463371e6691b1a794e97fa36b4:
cgroup/cpuset: Fix "suspicious RCU usage" lockdep warning (2022-02-03 05:59:01 -1000)
----------------------------------------------------------------
Eric W. Biederman (1):
cgroup-v1: Require capabilities to set release_agent
Michal Koutný (1):
cgroup/cpuset: Make child cpusets restrict parents on v1 hierarchy
Tianchen Ding (1):
cpuset: Fix the bug that subpart_cpus updated wrongly in update_cpumask()
Waiman Long (1):
cgroup/cpuset: Fix "suspicious RCU usage" lockdep warning
kernel/cgroup/cgroup-v1.c | 14 ++++++++++
kernel/cgroup/cpuset.c | 65 +++++++++++++++++++++++++++++++++++++----------
2 files changed, 65 insertions(+), 14 deletions(-)
--
tejun
next reply other threads:[~2022-02-03 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 16:13 Tejun Heo [this message]
2022-02-03 19:40 ` 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=Yfv/LMxqHSa3s5YS@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.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®