[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1401311315110.27318@chino.kir.corp.google.com>
Date: Fri, 31 Jan 2014 13:19:29 -0800 (PST)
From: David Rientjes <rientjes@...gle.com>
To: dormando <dormando@...ia.net>
cc: Alexei Starovoitov <alexei.starovoitov@...il.com>,
Eric Dumazet <eric.dumazet@...il.com>, netdev@...r.kernel.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Alexei Starovoitov <ast@...mgrid.com>
Subject: Re: kmem_cache_alloc panic in 3.10+
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@...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