From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Ingo Molnar <mingo@elte.hu>, Robert Love <rml@tech9.net>,
george anzinger <george@mvista.com>,
Zwane Mwaikambo <zwane@linuxpower.ca>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch] irqlock patch -G3. [was Re: odd memory corruptionin2.5.27?]
Date: Wed, 24 Jul 2002 01:03:29 -0700 [thread overview]
Message-ID: <20020724080329.GB25038@holomorphy.com> (raw)
In-Reply-To: <3D3E5E80.EA769517@zip.com.au>
Ingo Molnar wrote:
>> Code that relies on
>> cli/sti for atomicity should be pretty rare and limited, there's 1 known
>> case so far where it leads to bugs.
On Wed, Jul 24, 2002 at 01:00:00AM -0700, Andrew Morton wrote:
> Are you implying that all code which does spin_unlock() inside
> local_irq_disable() needs to be converted to use _raw_spin_unlock()?
> If so then, umm, ugh. I hope that the debug check is working
> for CONFIG_PREEMPT=n.
> BTW, what is the situation with spin_unlock_irq[restore]()? Seems
> that these will schedule inside local_irq_disable() quite a lot?
Since we're on the subject of preempt_schedule() being done at
inappropriate times, I'm seeing it being called and panicking the
machine before the per-cpu GDT, IDT, TSS, and LDT are loaded in
cpu_init() and suspect that may be a wee bit too early to be sane.
Cheers,
Bill
next prev parent reply other threads:[~2002-07-24 8:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 6:23 odd memory corruption in 2.5.27? Zwane Mwaikambo
2002-07-23 6:24 ` Zwane Mwaikambo
2002-07-23 6:26 ` Zwane Mwaikambo
2002-07-23 7:57 ` Trond Myklebust
2002-07-23 8:54 ` Zwane Mwaikambo
2002-07-23 20:32 ` george anzinger
2002-07-23 20:47 ` William Lee Irwin III
2002-07-23 23:28 ` [patch] irqlock patch -G3. [was Re: odd memory corruption in 2.5.27?] Ingo Molnar
2002-07-23 23:53 ` george anzinger
2002-07-23 23:56 ` Linus Torvalds
2002-07-24 0:07 ` Ingo Molnar
2002-07-24 2:15 ` Linus Torvalds
2002-07-24 8:59 ` [patch] irqlock patch 2.5.27-H3 Ingo Molnar
2002-07-24 1:08 ` [patch] irqlock patch -G3. [was Re: odd memory corruption in 2.5.27?] Robert Love
2002-07-24 3:13 ` [patch] irqlock patch -G3. [was Re: odd memory corruption in2.5.27?] Andrew Morton
2002-07-24 3:18 ` Linus Torvalds
2002-07-24 7:13 ` Ingo Molnar
2002-07-24 7:34 ` Ingo Molnar
2002-07-24 8:00 ` [patch] irqlock patch -G3. [was Re: odd memory corruptionin2.5.27?] Andrew Morton
2002-07-24 7:54 ` Ingo Molnar
2002-07-24 8:03 ` William Lee Irwin III [this message]
2002-07-24 8:06 ` Ingo Molnar
2002-07-24 8:15 ` William Lee Irwin III
2002-07-24 8:17 ` Ingo Molnar
2002-07-24 16:40 ` Linus Torvalds
2002-07-24 16:49 ` Robert Love
2002-07-24 20:56 ` [patch] irqlock patch -G3. [was Re: odd memorycorruptionin2.5.27?] george anzinger
2002-07-24 7:37 ` [patch] irqlock patch -G3. [was Re: odd memory corruption in2.5.27?] Ingo Molnar
2002-07-24 6:52 ` odd memory corruption in 2.5.27? Zwane Mwaikambo
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=20020724080329.GB25038@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@zip.com.au \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rml@tech9.net \
--cc=torvalds@transmeta.com \
--cc=trond.myklebust@fys.uio.no \
--cc=zwane@linuxpower.ca \
/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