Re: [discuss] Re: 2.6.16-rc5-mm3: spinlock bad magic on CPU#0 on AMD64

[Andi Kleen]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/