From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 17 Jan 2008 10:58:53 -0800 (PST) From: Christoph Lameter Subject: Re: crash in kmem_cache_init In-Reply-To: <20080117181222.GA24411@aepfle.de> Message-ID: References: <20080115150949.GA14089@aepfle.de> <84144f020801170414q7d408a74uf47a84b777c36a4a@mail.gmail.com> <20080117181222.GA24411@aepfle.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Olaf Hering Cc: Pekka Enberg , linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, Linux MM List-ID: On Thu, 17 Jan 2008, Olaf Hering wrote: > The patch does not help. Duh. We need to know more about the problem. > > --- linux-2.6.orig/mm/slab.c 2008-01-03 12:26:42.000000000 -0800 > > +++ linux-2.6/mm/slab.c 2008-01-09 15:59:49.000000000 -0800 > > @@ -2977,7 +2977,10 @@ retry: > > } > > l3 = cachep->nodelists[node]; > > > > - BUG_ON(ac->avail > 0 || !l3); > > + if (!l3) > > + return NULL; > > + > > + BUG_ON(ac->avail > 0); > > spin_lock(&l3->list_lock); > > > > /* See if we can refill from the shared array */ > > Is this hsupposed to go into cache_grow()? There is no NULL check > for l3. No its for cache_alloc_refill. cache_grow should only be called for nodes that have memory. l3 is always used before cache_grow is called. > freeing bootmem node 1 > Memory: 3496632k/3571712k available (6188k kernel code, 75080k reserved, 1324k data, 1220k bss, 304k init) > cache_grow(2781) swapper(0):c0,j4294937299 cp c0000000006a4fb8 !l3 Is there more backtrace information? What function called cache_grow? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org