linux-ext4 - Re: [PATCH] fix header check in ext4_ext_search

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: <49B5573A.4060407@redhat.com>
Date:	Mon, 09 Mar 2009 12:51:54 -0500
From:	Eric Sandeen <sandeen@...hat.com>
To:	Theodore Tso <tytso@....edu>
CC:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
	ext4 development <linux-ext4@...r.kernel.org>,
	David Dindorp <ddi@...ex.dk>
Subject: Re: [PATCH] fix header check in ext4_ext_search_right() for deep
 extent trees.

Theodore Tso wrote:
> On Mon, Mar 09, 2009 at 11:13:08AM -0500, Eric Sandeen wrote:
>>>> deep-tree-2.img.gz contains an extent tree of depth 4....
>>>>
>> I think this jives w/ what the reporter had, although in the e2image the
>> problematic inode only had depth 3 (at the time)
> 
> I'm downloading and decompressing the e2image from the reporter right
> now.  Have you tried mounting the e2image over the loop device with
> and without the patch?  That should be able to demonstrate the
> problem, and then prove that the patch fixes it.  I'll also dump out
> the extent tree from the reporter and try to create a small test case
> based on the inode in question.  (Inode #2621457, right?)
> 
>       	     	      		 		  - Ted

I have mounted it but I'm not sure that's sufficient to trip the case.

A dump of the inode in question from the e2image is at:

http://bugzilla.kernel.org/attachment.cgi?id=20449&action=view

(slightly massaged from default output)

-Eric
--
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