Date: Tue, 11 Nov 2003 09:00:23 -0800 (PST)
From: Linus Torvalds <torvalds@osdl.org>
To: Pascal Schmidt <der.eremit@email.de>
cc: linux-kernel@vger.kernel.org
Subject: Re: 2.9test9-mm1 and DAO ATAPI cd-burning corrupt
In-Reply-To: <E1AJbcD-0000Iw-00@neptune.local>
Message-ID: <Pine.LNX.4.44.0311110855070.30657-100000@home.osdl.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1141
Lines: 26


On Tue, 11 Nov 2003, Pascal Schmidt wrote:
> 
> Well, that person is me and I tried making it work with ide-cd. Got read
> support to work, submitted to Jens, you have it in your kernel. No luck
> with write support. I could get it to mount read-write and data actually
> made it to disk, but umount lead to a BUG_ON.

Hmm.. That looks "impossible", so it's most likely a serious bh corruption 
issue. But what corrupts it is hard to guess at - the actual trace to that 
point has nothing to do with the MO drive itself, so you've either hit a 
generic ext2 bug (hey, it's possible, I guess, but sounds very unlikely), 
or the ide-scsi driver has corrupted memory. 

The latter is obviously the more likely schenario, but it does require 
somebody with the MO device to actually try to figure out how the 
corruption occurs.. Probably with a big printk buffer and a lot of 
printk's..

			Linus

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