From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: 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 10:53:10 -0500 [thread overview]
Message-ID: <49B53B66.50806@redhat.com> (raw)
In-Reply-To: <20090309113619.GH5578@mit.edu>
Theodore Tso wrote:
> On Fri, Mar 06, 2009 at 02:50:51PM -0600, Eric Sandeen wrote:
>> This should resolve kernel.org bugzilla 12821
>>
>> I've not actually crafted a workload to exercise this code;
>> this is from inspection...
>
> Hmm, so I've been trying to create a test case, but the test cases
> I've created (which e2fsck say are fine) aren't causing complaints by
> the kernel.
>
> Please see:
>
> http://master.kernel.org/~tytso/deep-tree/
>
> deep-tree.img.gz contains an extent tree of depth 3, and
> deep-tree-2.img.gz contains an extent tree of depth 4....
>
> - Ted
I've had no trouble creating a deep tree, but I have had trouble making
it actually exercise the code in that loop.
I think the initial ext4_ext_find_extent() needs to land us in just the
right place such that the search_right must traverse back up & back down
the tree to get the nearest right allocation... I haven't sorted that
out yet.
I'd feel better w/ a testcase to demonstrate correctness too, but I'm
99.9% sure that the fix is correct by inspection, and would rather see
it get into .29 sooner than later unless you have strong misgivings.
-Eric
next prev parent reply other threads:[~2009-03-09 15:53 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 [this message]
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
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=49B53B66.50806@redhat.com \
--to=sandeen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).