From: Li Zefan <lizefan@huawei.com>
To: William Dauchy <wdauchy@gmail.com>
Cc: Tejun Heo <tj@kernel.org>, Hugh Dickins <hughd@google.com>,
Shawn Bohrer <shawn.bohrer@gmail.com>,
Michal Hocko <mhocko@suse.cz>, <cgroups@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Markus Blank-Burian <burian@muenster.de>
Subject: Re: 3.10.16 cgroup_mutex deadlock
Date: Tue, 3 Dec 2013 09:37:52 +0800 [thread overview]
Message-ID: <529D35F0.60108@huawei.com> (raw)
In-Reply-To: <CAJ75kXYKx67VaGYRs1nwataE2ra216qTB9Yks=MRGFN-c_b3uA@mail.gmail.com>
On 2013/12/2 18:31, William Dauchy wrote:
> Hi Li,
>
> On Mon, Nov 25, 2013 at 2:20 AM, Li Zefan <lizefan@huawei.com> wrote:
>> I'll do this after the patch hits mainline, if Tejun doesn't plan to.
>
> Do you have some news about it?
>
Tejun has already done the backport. :)
It has been included in 3.10.22, which will be released in a couple of days.
http://article.gmane.org/gmane.linux.kernel.stable/71292
next prev parent reply other threads:[~2013-12-03 1:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 22:06 Shawn Bohrer
2013-11-12 10:17 ` Li Zefan
2013-11-12 14:31 ` Michal Hocko
2013-11-12 15:55 ` Shawn Bohrer
2013-11-12 16:55 ` Michal Hocko
2013-11-14 22:56 ` Shawn Bohrer
2013-11-15 6:24 ` Tejun Heo
2013-11-15 7:54 ` Tejun Heo
2013-11-18 2:17 ` Hugh Dickins
2013-11-18 20:10 ` Shawn Bohrer
2013-11-19 2:55 ` Li Zefan
2013-11-20 22:47 ` Shawn Bohrer
2013-11-22 20:59 ` William Dauchy
2013-11-22 22:18 ` Tejun Heo
2013-11-22 22:54 ` William Dauchy
2013-11-25 1:20 ` Li Zefan
2013-12-02 10:31 ` William Dauchy
2013-12-03 1:37 ` Li Zefan [this message]
2013-11-22 22:17 ` [PATCH cgroup/for-3.13-fixes] cgroup: use a dedicated workqueue for cgroup destruction Tejun Heo
2013-11-24 18:23 ` Hugh Dickins
2013-11-25 1:16 ` Li Zefan
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=529D35F0.60108@huawei.com \
--to=lizefan@huawei.com \
--cc=burian@muenster.de \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=shawn.bohrer@gmail.com \
--cc=tj@kernel.org \
--cc=wdauchy@gmail.com \
/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
Powered by JetHome