From: Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Hillf Danton <dhillf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
cgroups <cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
KAMEZAWA Hiroyuki
<kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>,
Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>,
Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
Subject: Re: [BUG] potential deadlock led by cpu_hotplug lock (memcg involved)
Date: Tue, 12 Mar 2013 17:35:51 +0800 [thread overview]
Message-ID: <513EF6F7.90002@huawei.com> (raw)
In-Reply-To: <CAJd=RBB7GVp_Ry30SuZVa-FgOogEZ43UnXOGvVKesV=Qk96UDA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 2013/3/12 16:32, Hillf Danton wrote:
> On Tue, Mar 12, 2013 at 2:36 PM, Li Zefan <lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org> wrote:
>> Seems a new bug in 3.9 kernel?
>>
> Bogus info, perhaps.
>
No matter it's a real bug or it's false positive, we need to make
lockdep happy.
next prev parent reply other threads:[~2013-03-12 9:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 6:36 [BUG] potential deadlock led by cpu_hotplug lock (memcg involved) Li Zefan
2013-03-12 8:32 ` Hillf Danton
[not found] ` <CAJd=RBB7GVp_Ry30SuZVa-FgOogEZ43UnXOGvVKesV=Qk96UDA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-12 9:35 ` Li Zefan [this message]
2013-03-12 10:15 ` Michal Hocko
[not found] ` <20130312101555.GB30758-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2013-03-12 11:07 ` Michal Hocko
[not found] ` <20130312110750.GC30758-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2013-03-12 13:05 ` [PATCH] device: separate all subsys mutexes (was: Re: [BUG] potential deadlock led by cpu_hotplug lock (memcg involved)) Michal Hocko
2013-03-12 13:34 ` Greg Kroah-Hartman
[not found] ` <20130312133446.GA3514-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-03-12 16:21 ` [PATCH -v2] " Michal Hocko
[not found] ` <20130312162119.GB5963-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2013-03-12 18:47 ` Greg Kroah-Hartman
[not found] ` <20130312130504.GD30758-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2013-03-12 15:28 ` [PATCH] " Peter Zijlstra
2013-03-12 15:43 ` Greg Kroah-Hartman
[not found] ` <20130312154341.GB18852-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-03-12 16:09 ` Peter Zijlstra
2013-03-12 16:17 ` Greg Kroah-Hartman
2013-03-12 16:13 ` Michal Hocko
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=513EF6F7.90002@huawei.com \
--to=lizefan-hv44wf8li93qt0dzr+alfa@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dhillf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=mhocko-AlSwsSmVLrQ@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.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