Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932738AbaAaVTs (ORCPT ); Fri, 31 Jan 2014 16:19:48 -0500 Received: from mail-pd0-f180.google.com ([209.85.192.180]:60128 "EHLO mail-pd0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752785AbaAaVTq (ORCPT ); Fri, 31 Jan 2014 16:19:46 -0500 Date: Fri, 31 Jan 2014 13:19:29 -0800 (PST) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: dormando cc: Alexei Starovoitov , Eric Dumazet , netdev@vger.kernel.org, "linux-kernel@vger.kernel.org" , Alexei Starovoitov Subject: Re: kmem_cache_alloc panic in 3.10+ In-Reply-To: Message-ID: References: <1390062576.31367.519.camel@edumazet-glaptop2.roam.corp.google.com> <1391134615.28432.83.camel@edumazet-glaptop2.roam.corp.google.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 30 Jan 2014, dormando wrote: > > > I really wonder... it looks like a possible in SLUB. (might be already > > > fixed) > > > > > > Could you try using SLAB instead ? > > > > try config_slub_debug_on=y ? it should catch double free and other things. > > > > Any slowdowns/issues with that? CONFIG_SLUB_DEBUG_ON will definitely be slower but can help to identify any possible corruption issues. I'm wondering if you have CONFIG_MEMCG enabled and are actually allocating slab in a non-root memcg? What does /proc/self/cgroup say? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/