linux-ext4 - Re: EXT4 corruption on Linus latest tree.

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] [day] [month] [year] [list]

Message-ID: <20130227180302.GB16966@thunk.org>
Date:	Wed, 27 Feb 2013 13:03:02 -0500
From:	Theodore Ts'o <tytso@....edu>
To:	"gnehzuil.liu" <gnehzuil.liu@...il.com>
Cc:	Dave Jones <davej@...hat.com>, Borislav Petkov <bp@...en8.de>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: EXT4 corruption on Linus latest tree.

On Thu, Feb 28, 2013 at 01:07:10AM +0800, gnehzuil.liu wrote:
> 
> Thanks for the report.  From the result, I think extent status tree
> is root cause because of wrong logical-to-physical block mapping.  I
> am very sorry about that.  I will try to fix the bug ASAP.

Here's a hint as to what's going on:

% bc
bc 1.06.95
Copyright 1991-1994, 1997, 1998, 2000, 2004, 2006 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty'. 
obase=16
# This is the block number printed in the error message
152052301
910224D

# This is the block number reported by debugfs
688923213
2910224D

It looks like something in the code is masking off the low 25 bits, so
we're losing the higher bits from the physical block number.  That
should be pretty easy to find and fix....

       	  	      	      	  - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html