From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
ext4 development <linux-ext4@vger.kernel.org>,
David Dindorp <ddi@dubex.dk>
Subject: Re: [PATCH] fix header check in ext4_ext_search_right() for deep extent trees.
Date: Mon, 09 Mar 2009 12:51:54 -0500 [thread overview]
Message-ID: <49B5573A.4060407@redhat.com> (raw)
In-Reply-To: <20090309173459.GB8840@mit.edu>
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
prev parent reply other threads:[~2009-03-09 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 20:50 [PATCH] fix header check in ext4_ext_search_right() for deep extent trees Eric Sandeen
2009-03-09 4:59 ` Aneesh Kumar K.V
2009-03-09 11:36 ` Theodore Tso
2009-03-09 15:53 ` Eric Sandeen
2009-03-09 16:01 ` Aneesh Kumar K.V
2009-03-09 16:13 ` Eric Sandeen
2009-03-09 17:34 ` Theodore Tso
2009-03-09 17:51 ` Eric Sandeen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49B5573A.4060407@redhat.com \
--to=sandeen@redhat.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=ddi@dubex.dk \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.