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, Peter Zijlstra <peterz@infradead.org>
Subject: [GIT PULL] cgroup fixes for v4.5-rc3
Date: Wed, 10 Feb 2016 12:32:27 -0500 [thread overview]
Message-ID: <20160210173227.GP3741@mtj.duckdns.org> (raw)
Hello, Linus.
cgroup fixes for v4.5-rc3.
* The destruction path of cgroup objects are asynchronous and
multi-staged and some of them ended up destroying parents before
children leading to failures in cpu and memory controllers. Ensure
that parents are always destroyed after children.
* cpuset mm node migration was performed synchronously while holding
threadgroup and cgroup mutexes and the recent threadgroup locking
update resulted in a possible deadlock. The migration is best
effort and shouldn't have been performed under those locks to begin
with. Made asynchronous.
* Minor documentation fix.
Thanks.
The following changes since commit 3e1e21c7bfcfa9bf06c07f48a13faca2f62b3339:
Merge branch 'for-4.5/nvme' of git://git.kernel.dk/linux-block (2016-01-21 19:58:02 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-4.5-fixes
for you to fetch changes up to 9a2ddda572a002633a64b1ae5f4bc49cfcbf495f:
Documentation: cgroup: Fix 'cgroup-legacy' -> 'cgroup-v1' (2016-01-29 06:11:57 -0500)
----------------------------------------------------------------
Tejun Heo (3):
cpuset: make mm migration asynchronous
cgroup: make sure a parent css isn't offlined before its children
cgroup: make sure a parent css isn't freed before its children
W. Trevor King (1):
Documentation: cgroup: Fix 'cgroup-legacy' -> 'cgroup-v1'
Documentation/cgroup-v2.txt | 2 +-
include/linux/cgroup-defs.h | 6 ++++
include/linux/cpuset.h | 6 ++++
kernel/cgroup.c | 31 +++++++++++++++-----
kernel/cpuset.c | 71 +++++++++++++++++++++++++++++++--------------
5 files changed, 85 insertions(+), 31 deletions(-)
--
tejun
reply other threads:[~2016-02-10 17:32 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=20160210173227.GP3741@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).