Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757580AbYBSPxx (ORCPT ); Tue, 19 Feb 2008 10:53:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752959AbYBSPxn (ORCPT ); Tue, 19 Feb 2008 10:53:43 -0500 Received: from courier.cs.helsinki.fi ([128.214.9.1]:38568 "EHLO mail.cs.helsinki.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751557AbYBSPxm (ORCPT ); Tue, 19 Feb 2008 10:53:42 -0500 Message-ID: <47BAFB42.9000806@cs.helsinki.fi> Date: Tue, 19 Feb 2008 17:52:34 +0200 From: Pekka Enberg User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Ingo Molnar CC: Mathieu Desnoyers , Torsten Kaiser , Linus Torvalds , Linux Kernel Mailing List , Christoph Lameter , yanmin_zhang@linux.intel.com Subject: Re: Linux 2.6.25-rc2 References: <64bb37e0802161338j306c1357m25bc224f09e6b7cd@mail.gmail.com> <20080219061107.GA23229@elte.hu> <64bb37e0802182254l49b10cbblc23f8a83d189ff8e@mail.gmail.com> <84144f020802182321x452888bai639c71ea2a5067da@mail.gmail.com> <20080219140230.GA32236@Krystal> <84144f020802190621s509dbe7gc8e5609d94aca9b4@mail.gmail.com> <84144f020802190638i4a364d19o8986a457e76ec187@mail.gmail.com> <20080219145554.GE21176@elte.hu> In-Reply-To: <20080219145554.GE21176@elte.hu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2005 Lines: 54 Ingo Molnar wrote: > * Pekka Enberg wrote: > >>> Yes, this can happen. Are you saying it is not safe to be in the >>> lockless path when an IRQ triggers? >> Hmm. The barrier() in slab_free() looks fishy. The comment says it's >> there to make sure we've retrieved c->freelist before c->page but then >> it uses a _compiler barrier_ which doesn't affect the CPU and the >> reads may still be re-ordered... Not sure if that matters here though. > > find a fix patch for that below - most systems affected seem to be SMP > ones. > > If this (or my other patch) indeed solves the problem i'd still favor a > full revert of the SLUB_FASTPATH (commit 1f84260c8ce3b1ce26d4), it looks > quite un-cooked and quite un-tested for multiple independent reasons. > > Sigh, why do i again have to be the messenger who brings the bad news to > SLUB land, and again when poor Christoph went on vacation? :-/ > > Ingo > > --------------------------> > Subject: SLUB: barrier fix > From: Ingo Molnar > > --- > mm/slub.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > Index: linux/mm/slub.c > =================================================================== > --- linux.orig/mm/slub.c > +++ linux/mm/slub.c > @@ -1862,7 +1862,7 @@ static __always_inline void slab_free(st > debug_check_no_locks_freed(object, s->objsize); > do { > freelist = c->freelist; > - barrier(); > + smp_mb(); > /* > * If the compiler would reorder the retrieval of c->page to > * come before c->freelist then an interrupt could Torsten/Yamin, does this fix things for you? What about reverting commit 1f84260c8ce3b1ce26d4c1d6dedc2f33a3a29c0c ("SLUB: Alternate fast paths using cmpxchg_local")? Pekka -- 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/