Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S937494AbWLFT36 (ORCPT ); Wed, 6 Dec 2006 14:29:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S937517AbWLFT36 (ORCPT ); Wed, 6 Dec 2006 14:29:58 -0500 Received: from omx2-ext.sgi.com ([192.48.171.19]:37911 "EHLO omx2.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S937494AbWLFT34 (ORCPT ); Wed, 6 Dec 2006 14:29:56 -0500 Date: Wed, 6 Dec 2006 11:29:42 -0800 (PST) From: Christoph Lameter To: Matthew Wilcox cc: Linus Torvalds , Russell King , David Howells , Andrew Morton , linux-arm-kernel@lists.arm.linux.org.uk, Linux Kernel Mailing List , linux-arch@vger.kernel.org Subject: Re: [PATCH] WorkStruct: Implement generic UP cmpxchg() where an arch doesn't support it In-Reply-To: <20061206192647.GW3013@parisc-linux.org> Message-ID: References: <20061206164314.19870.33519.stgit@warthog.cambridge.redhat.com> <20061206192647.GW3013@parisc-linux.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 723 Lines: 18 On Wed, 6 Dec 2006, Matthew Wilcox wrote: > It's just been pointed out to me that the parisc one isn't safe. > > imagine variable X is set to 3 > CPU A issues cmpxchg(&X, 3, 5) > you'd expect that to change X to 5 > but what if CPU B assigns 6 to X between cmpxchg reading X > and it setting X? The same could happen with a regular cmpxchg. Cmpxchg changes it to 5 and then other cpu performs a store before the next instruction. - 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/