mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
	geert@linux-m68k.org, zippel@linux-m68k.org,
	linux-m68k@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: 2.6.16-rc regression: m68k CONFIG_RMW_INSNS=n compile broken
Date: Sat, 4 Mar 2006 00:43:23 +0100	[thread overview]
Message-ID: <20060303234323.GF9295@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0603031515321.22647@g5.osdl.org>

On Fri, Mar 03, 2006 at 03:22:42PM -0800, Linus Torvalds wrote:
> 
> 
> On Sat, 4 Mar 2006, Adrian Bunk wrote:
> > 
> > It seems the problem is that in the CONFIG_RMW_INSNS=n case, there's no 
> > cmpxchg #define in include/asm-m68k/system.h required for the 
> > atomic_add_unless #define in include/asm-m68k/atomic.h.
> 
> Hmm. It seems like it never has been there.. Do you know what brought this 
> on? Was it Nick's RCU changes from "rcuref_dec_and_test()" to 
> "atomic_dec_and_test()" and friends? 

It was Nick's commit 8426e1f6af0fd7f44d040af7263750c5a52f3cc3 that added 
atomic_inc_not_zero(), and Nick's patch that changed fs/file_table.c 
from rcuref_dec_and_test() to atomic_dec_and_test() exposed this 
problem.

> Judging by your error messages, I _think_ it's the "atomic_inc_not_zero()" 
> that gets expanded to a cmpxchg() that simply doesn't exist on m68k and 
> never has.

Exactly, that's what I wanted to say in my report.

> I guess we've never depended on cmpxchg before. Or am I missing something?

It seems this is the case.

And as far as I can see, m68k is the only architecture where cmpxchg 
isn't always available.

> 		Linus

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-03-03 23:43 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-27  5:27 Linux v2.6.16-rc5 Linus Torvalds
2006-02-27  5:51 ` Jeff Garzik
2006-02-27  6:21   ` Randy.Dunlap
2006-02-27  6:52     ` Jeff Garzik
2006-02-27  8:13   ` Paul Rolland
2006-02-27 18:04   ` Francois Romieu
2006-02-27 18:38     ` Jeff Garzik
2006-02-27 22:24       ` Pull request for 'for-jeff' branch Francois Romieu
2006-02-27  6:13 ` 2.6.16-rc5: known regressions Adrian Bunk
2006-02-27  6:26   ` Ryan Phillips
2006-02-27  6:39     ` Vojtech Pavlik
2006-02-27  9:14       ` 2.6.16-rc5: known regressions (ps2 mouse/keyboard issues) Duncan
2006-02-27  6:54   ` 2.6.16-rc5: known regressions Jeff Garzik
2006-02-27  7:08     ` Adrian Bunk
2006-02-28  9:40       ` Jens Axboe
2006-03-01  0:17         ` Randy.Dunlap
2006-03-04 13:18           ` Adrian Bunk
2006-02-27 13:36   ` Mark Lord
2006-02-27 14:09   ` Pavel Machek
2006-03-02 14:00   ` [v4l-dvb-maintainer] " Mauro Carvalho Chehab
2006-03-04 13:27     ` Adrian Bunk
2006-03-04 13:39       ` Mauro Carvalho Chehab
     [not found]     ` <6dd519ae0603080313o4e7b8a61h5002125c33a0e008@mail.gmail.com>
2006-03-08 20:29       ` Mauro Carvalho Chehab
2006-03-08 22:52         ` Hartmut Hackmann
2006-02-27  7:28 ` Linux v2.6.16-rc5 Dave Jones
2006-02-27 11:20   ` Jens Axboe
2006-02-27 22:42     ` Neil Brown
2006-02-27  7:42 ` Dave Jones
2006-02-27  9:28   ` Nick Piggin
2006-02-27 19:52 ` Rene Herman
2006-02-27 22:51   ` Andrew Morton
2006-02-27 23:32     ` Rene Herman
2006-02-28  1:05       ` Rene Herman
2006-02-28  1:12         ` Andrew Morton
2006-02-28  9:38 ` Linux v2.6.16-rc5 - regression Peter Hagervall
2006-02-28 10:03   ` Andrew Morton
2006-02-28 11:41     ` Peter Hagervall
2006-02-28 11:49       ` Peter Hagervall
2006-02-28 12:43 ` Linux v2.6.16-rc5 Christoph Hellwig
2006-03-03 16:00 ` Mark Rosenstand
2006-03-03 23:01 ` 2.6.16-rc regression: m68k CONFIG_RMW_INSNS=n compile broken Adrian Bunk
2006-03-03 23:22   ` Linus Torvalds
2006-03-03 23:43     ` Adrian Bunk [this message]
2006-03-03 23:59     ` Andrew Morton
2006-03-04 14:01       ` Roman Zippel
2006-03-04 14:12         ` Nick Piggin
2006-03-04 20:28           ` Andrew Morton
2006-03-08 11:24             ` [2.6 patch] m68k: fix cmpxchg compile errors if CONFIG_RMW_INSNS=n Adrian Bunk
2006-03-05 14:09 ` Linux v2.6.16-rc5 Olaf Hering
2006-03-05 18:59   ` Olaf Hering
2006-03-05 20:02     ` Linus Torvalds
2006-03-05 20:42       ` Olaf Hering
2006-03-05 21:50         ` Paul Mackerras
2006-03-05 22:22           ` Olaf Hering
2006-03-05 22:44             ` Olaf Hering
2006-03-06  7:48               ` Olaf Hering
2006-03-06 16:48           ` Olaf Hering
2006-03-06 22:20             ` Olaf Hering
2006-03-06 23:02               ` Olaf Hering
2006-03-11 21:59                 ` Olaf Hering
2006-03-05 22:03 ` Mathieu Chouquet-Stringer
2006-03-06  2:12   ` Linus Torvalds
2006-03-06  4:44 2.6.16-rc regression: m68k CONFIG_RMW_INSNS=n compile broken Suzanne Wood
2006-03-06 15:35 ` Dipankar Sarma
2006-03-06 16:13 Suzanne Wood
2006-03-06 16:48 ` Dipankar Sarma
2006-03-07  1:14 Suzanne Wood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060303234323.GF9295@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=torvalds@osdl.org \
    --cc=zippel@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®