From mboxrd@z Thu Jan 1 00:00:00 1970 From: dormando Subject: Re: kmem_cache_alloc panic in 3.10+ Date: Fri, 31 Jan 2014 15:43:43 -0800 (PST) Message-ID: References: <1390062576.31367.519.camel@edumazet-glaptop2.roam.corp.google.com> <1391134615.28432.83.camel@edumazet-glaptop2.roam.corp.google.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Alexei Starovoitov , Eric Dumazet , netdev@vger.kernel.org, "linux-kernel@vger.kernel.org" , Alexei Starovoitov To: David Rientjes Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org 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!