From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Li Zefan <lizefan@huawei.com>,
Johannes Weiner <hannes@cmpxchg.org>,
cgroups@vger.kernel.org, Roman Gushchin <guro@fb.com>
Subject: [GIT PULL] cgroup fixes for v4.13-rc3
Date: Mon, 31 Jul 2017 08:43:53 -0700 [thread overview]
Message-ID: <20170731154353.GD447614@devbig577.frc2.facebook.com> (raw)
Hello, Linus.
Several cgroup bug fixes.
* cgroup core was calling a migration callback on empty migrations,
which could make cpuset crash.
* There was a very subtle bug where the controller interface files
aren't created directly when cgroup2 is mounted. Because later
operations create them, this bug didn't get noticed earlier.
* Failed writes to cgroup.subtree_control were incorrectly returning
0.
The following changes since commit cee37d83e6d9ada1c2254c73bac7955f9e048d22:
Merge branch 'work.read_write' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs (2017-07-07 21:48:15 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-4.13-fixes
for you to fetch changes up to 3c74541777302eec43a0d1327c4d58b8659a776b:
cgroup: fix error return value from cgroup_subtree_control() (2017-07-23 08:15:17 -0400)
----------------------------------------------------------------
Tejun Heo (3):
cgroup: don't call migration methods if there are no tasks to migrate
cgroup: create dfl_root files on subsys registration
cgroup: fix error return value from cgroup_subtree_control()
kernel/cgroup/cgroup-internal.h | 3 ++
kernel/cgroup/cgroup.c | 66 +++++++++++++++++++++++------------------
2 files changed, 40 insertions(+), 29 deletions(-)
--
tejun
reply other threads:[~2017-07-31 15:43 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=20170731154353.GD447614@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.