From: Andi Kleen <ak@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org, Mingming Cao <cmm@us.ibm.com>,
Badari Pulavarty <pbadari@us.ibm.com>
Subject: Re: [discuss] Re: 2.6.16-rc5-mm3: spinlock bad magic on CPU#0 on AMD64
Date: Sun, 12 Mar 2006 16:10:31 +0100 [thread overview]
Message-ID: <200603121610.31881.ak@suse.de> (raw)
In-Reply-To: <20060312142654.650b90fb.akpm@osdl.org>
On Sunday 12 March 2006 23:26, Andrew Morton wrote:
>
> It's a pretty vile backtrace. I supposed you have CONFIG_FRAME_POINTER=n.
Won't make a difference because the oops backtracer doesn't
use them.
> Still. It seems that what's happened is that we took a pagefault while
> reiserfs had a transaction open. The fault is against a mmapped ext3 file
> and we ended up in the recently-reworked ext3_get_block() which tests
> journal_current_handle() to work out whether we're in a write or a read.
> oops. The presence of reiserfs journal_info makes it decide it's a write,
> not a read so it starts treating a reiserfs journal_info as an ext3 one.
>
> The code used to work OK because it was only for direct-IO, which doesn't
> get recurred into like this. But it got used for regular I/O in -mm.
Oops. Can this happen in more situations?
-Andi
next prev parent reply other threads:[~2006-03-12 22:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 23:24 2.6.16-rc5-mm3: spinlock bad magic on CPU#0 on AMD64 Rafael J. Wysocki
2006-03-11 23:36 ` Andrew Morton
2006-03-12 10:27 ` Rafael J. Wysocki
2006-03-12 12:49 ` [discuss] " Rafael J. Wysocki
2006-03-12 22:26 ` Andrew Morton
2006-03-12 15:10 ` Andi Kleen [this message]
2006-03-12 23:23 ` Andrew Morton
2006-03-13 11:34 ` Rafael J. Wysocki
2006-03-13 11:45 ` Andrew Morton
2006-03-13 12:07 ` Rafael J. Wysocki
2006-03-13 16:02 ` Badari Pulavarty
2006-03-13 18:12 ` Rafael J. Wysocki
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=200603121610.31881.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=rjw@sisk.pl \
/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