Re: kmem_cache_alloc panic in 3.10+

[dormando]

On Fri, 31 Jan 2014, David Rientjes wrote:

> On Fri, 31 Jan 2014, dormando wrote:
>
> > > 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?
> > >
> >
> > /proc/self/cgroup is empty on these hosts. CONFIG_MEMCG is enabled though.
> >
>
> It _looks_ like the cmpxchg_double() so seeing if there is anything else
> funny going on with CONFIG_SLUB_DEBUG_ON would definitely be helpful;
> otherwise, try using CONFIG_SLAB is Eric suggested and seeing if the
> problem goes away.
>

chpxchg_double()? that's not related to the 62713c4b fix right?

I'll see what I can do.. it's going to take a long time to iterate on this
though.

Thanks for the suggestions!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/