[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1408281030510.6401@gentwo.org>
Date: Thu, 28 Aug 2014 10:31:26 -0500 (CDT)
From: Christoph Lameter <cl@...ux.com>
To: Sasha Levin <sasha.levin@...cle.com>
cc: Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
LKML <linux-kernel@...r.kernel.org>,
"davej @gmail-imap.l.google.com>> Dave Jones" <davej@...hat.com>
Subject: Re: mm: slub: circular dependency between slab_mutex and
cpu_hotplug
On Thu, 28 Aug 2014, Sasha Levin wrote:
> While fuzzing with trinity inside a KVM tools guest running the latest -next
> kernel, I've stumbled on the following spew:
This looks to me more to be a cpu hotplug issue.
>
> [ 7841.323177] Possible unsafe locking scenario:
> [ 7841.323177]
> [ 7841.323177] CPU0 CPU1
> [ 7841.323177] ---- ----
> [ 7841.323177] lock(cpu_hotplug.lock#2);
> [ 7841.323177] lock((oom_notify_list).rwsem);
> [ 7841.323177] lock(cpu_hotplug.lock#2);
> [ 7841.323177] lock(slab_mutex);
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists