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 changes for v5.17-rc1
Date: Mon, 10 Jan 2022 07:46:32 -1000 [thread overview]
Message-ID: <Ydxw+LLhEmi5B/Re@slm.duckdns.org> (raw)
Hello, Linus.
Nothing too interesting. The only two noticeable changes are a subtle cpuset
behavior fix and trace event id field being expanded to u64 from int. Most
others are code cleanups.
Thanks.
The following changes since commit 8ab774587903771821b59471cc723bba6d893942:
Merge tag 'trace-v5.16-5' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace (2021-11-14 19:07:19 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-5.17
for you to fetch changes up to d4296faebd337e5f76c0fddb815de33d2b0ad118:
cpuset: convert 'allowed' in __cpuset_node_allowed() to be boolean (2022-01-07 12:05:52 -1000)
----------------------------------------------------------------
Michal Koutný (1):
cgroup: rstat: Mark benign data race to silence KCSAN
Qi Zheng (1):
cpuset: convert 'allowed' in __cpuset_node_allowed() to be boolean
Waiman Long (1):
cgroup/cpuset: Don't let child cpusets restrict parent in default hierarchy
Wei Yang (5):
cgroup: get the wrong css for css_alloc() during cgroup_init_subsys()
cgroup: fix a typo in comment
cgroup: return early if it is already on preloaded list
cgroup: rstat: explicitly put loop variant in while
cgroup/rstat: check updated_next only for root
William Kucharski (1):
cgroup: Trace event cgroup id fields should be u64
include/linux/cgroup-defs.h | 2 +-
include/trace/events/cgroup.h | 12 +++++-----
kernel/cgroup/cgroup.c | 6 ++---
kernel/cgroup/cpuset.c | 16 ++++----------
kernel/cgroup/rstat.c | 51 ++++++++++++++++++++-----------------------
5 files changed, 38 insertions(+), 49 deletions(-)
--
tejun
next reply other threads:[~2022-01-10 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 17:46 Tejun Heo [this message]
2022-01-11 18: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=Ydxw+LLhEmi5B/Re@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®