[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1111211539420.10548@router.home>
Date: Mon, 21 Nov 2011 15:43:10 -0600 (CST)
From: Christoph Lameter <cl@...ux.com>
To: Pekka Enberg <penberg@...nel.org>
cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Markus Trippelsdorf <markus@...ppelsdorf.de>,
Eric Dumazet <eric.dumazet@...il.com>,
"Alex,Shi" <alex.shi@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Matt Mackall <mpm@...enic.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Tejun Heo <tj@...nel.org>,
Christian Kujau <lists@...dbynature.de>
Subject: Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413
On Mon, 21 Nov 2011, Pekka Enberg wrote:
> Does CONFIG_SLAB make all the issues go away or are you still able to
> reproduce corruption with it? I'm asking because we have the per-cpu
> partial list patches in 3.2-rc1 and I'd like to rule them out as a
> suspect.
SLAB does not have the same capabilities to detect corruption.
You can disable most the cpu partial functionality by setting
/sys/kernel/slab/*/cpu_partial
to 0
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists