Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261725AbVEJSXf (ORCPT ); Tue, 10 May 2005 14:23:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261726AbVEJSXf (ORCPT ); Tue, 10 May 2005 14:23:35 -0400 Received: from fire.osdl.org ([65.172.181.4]:45804 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S261725AbVEJSXc (ORCPT ); Tue, 10 May 2005 14:23:32 -0400 Date: Tue, 10 May 2005 11:22:24 -0700 From: Andrew Morton To: "Rafael J. Wysocki" Cc: ak@suse.de, linux-kernel@vger.kernel.org, axboe@suse.de, alexn@dsv.su.se, lnxluv@yahoo.com, Christoph Lameter Subject: Re: [BUG][Resend] 2.6.12-rc3-mm3: Kernel BUG at "mm/slab.c":1219 [update] Message-Id: <20050510112224.761f5d68.akpm@osdl.org> In-Reply-To: <200505101443.31229.rjw@sisk.pl> References: <200505092239.37834.rjw@sisk.pl> <20050509145424.6ffba49a.akpm@osdl.org> <200505101443.31229.rjw@sisk.pl> X-Mailer: Sylpheed version 1.0.0 (GTK+ 1.2.10; i386-vine-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1488 Lines: 34 "Rafael J. Wysocki" wrote: > > > Clearly init_bio() is not passing in a NULL `name' parameter. Maybe the > > backtrace is screwed due to dopey gcc autoinlining and the bad caller is > > really biovec_init_slabs(). Try removing the > > __cacheline_aligned_mostly_readonly from the declaration of bvec_slabs[]. > > Heh, it boots without the __cacheline_aligned_mostly_readonly (ie the BUG is > only triggered if the __cacheline_aligned_mostly_readonly is present in the > declaration of bvec_slabs[]). I've double-checked it. Interesting ... ;-) oops. +#ifdef CONFIG_X86 +#define __cacheline_aligned_mostly_readonly \ + __attribute__((__aligned__(SMP_CACHE_BYTES), \ + __section__(".data.mostly_readonly"))) +#else +#define __cacheline_aligned_mostly_readonly __cacheline_aligned +#endif So on x86_64 we're putting __cacheline_aligned_mostly_readonly stuff into a section which is not implemented anywhere. I'm rather surprised that the kernel linked at all. But I'm more surprised that it mysteriously oopsed. Oh well, I'll change that to CONFIG_X86 && !CONFIG_X86_64, thanks. Or maybe Christoph wants to rustle up the x86_64 patch? We really should patch all architectures if we're going to do this thing. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/