Re: kmem_cache_alloc panic in 3.10+
From: David Rientjes <rientjes@google.com>
Date: 2014-01-31 21:19:48
Also in:
lkml
From: David Rientjes <rientjes@google.com>
Date: 2014-01-31 21:19:48
Also in:
lkml
On Thu, 30 Jan 2014, dormando wrote:
quoted
quoted
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?