All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: trond.myklebust@fys.uio.no, tglx@linutronix.de, mingo@redhat.com,
	hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.24-rc5 x86 architecture no longer Oopses...
Date: Fri, 21 Dec 2007 02:42:11 -0800	[thread overview]
Message-ID: <20071221024211.f4207136.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071221102727.GB22452@elte.hu>

On Fri, 21 Dec 2007 11:27:27 +0100 Ingo Molnar <mingo@elte.hu> wrote:

> > local_read_flags().
> > 
> > > that should have been raw_local_irq_save(flags)!
> > 
> > So raw_local_save_flags() and raw_local_irq_save() have different semantics.
> > 
> > omigawd, what have we done?
> 
> i really tried to get this fixed years ago - but did not think of 
> local_read_flags as a solution. The patch below fixes this.
> 
> (if it's too burdensome to carry right now then i can regenerate this 
> patch in 30 seconds in the 2.6.25 merge window - but please remind me 
> then. Perhaps put in a patch into your queue that adds a comment to 
> remind me :-) )

I'd suggest that we add a local_read_flags() along with local_save_flags().
Then I can merge the parts of the patch which don't get destroyed by ongoing
churn and then we can come in and clean up the stragglers later.

box:/usr/src/25> grep -l local_save_flags patches/*.patch 
patches/git-perfmon.patch
patches/git-sh.patch
patches/git-x86.patch
patches/i386-use-raw_smp_processor_id-in-die.patch
patches/mn10300-add-the-mn10300-am33-architecture-to-the-kernel.patch
patches/origin.patch



  reply	other threads:[~2007-12-21 10:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-20 22:40 Linux 2.6.24-rc5 x86 architecture no longer Oopses Trond Myklebust
2007-12-20 22:54 ` Andrew Morton
2007-12-20 22:56   ` Andrew Morton
2007-12-20 23:06     ` Trond Myklebust
2007-12-21  0:55     ` Rafael J. Wysocki
2007-12-21 10:19       ` Ingo Molnar
2007-12-20 23:04   ` Trond Myklebust
2007-12-20 23:47   ` Ingo Molnar
2007-12-21  0:02     ` Andrew Morton
2007-12-21  0:05       ` Ingo Molnar
2007-12-21  0:19     ` Andrew Morton
2007-12-21  0:30       ` Ingo Molnar
2007-12-21  0:40         ` Andrew Morton
2007-12-21  0:44           ` Ingo Molnar
2007-12-21 10:27           ` Ingo Molnar
2007-12-21 10:42             ` Andrew Morton [this message]
2007-12-21 11:12               ` Ingo Molnar
2007-12-21 11:34                 ` Andrew Morton
2007-12-21 12:31                   ` Ingo Molnar

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=20071221024211.f4207136.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=trond.myklebust@fys.uio.no \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.