linux-kernel - Re: 2.6.18-mm2: ext3 BUG?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0610061129040.12556@twin.jikos.cz>
Date:	Fri, 6 Oct 2006 11:33:36 +0200 (CEST)
From:	Jiri Kosina <jikos@...os.cz>
To:	Andrew Morton <akpm@...l.org>
cc:	Jiri Slaby <jirislaby@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	sct@...hat.com, adilger@...sterfs.com,
	ext2-devel@...ts.sourceforge.net
Subject: Re: 2.6.18-mm2: ext3 BUG?

On Thu, 5 Oct 2006, Andrew Morton wrote:

> Don't know.  The usual diagnosis for this sort of thing is "your disk 
> shat itself".  Could be a bad disk, bad power supply, bad memory, some 
> piece of kernel code went and trashed some memory, bug in the driver.  
> It's a mystery, sorry.

Actually I have also experienced some ext3 corruption (*) on my virtual 
machine under qemu emulation with 2.6.18-mm3, but I thought my previous 
other "strange" activities were guilty. Now it seems that there could be 
indeed something rotten in ext3 driver. Will try to reproduce, and if I am 
able to do so, I will bisect.

(*) Similar symptoms to the original poster - just fsck finding a few 
orphaned entries and lost blocks, etc.

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