From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Eric Sandeen <sandeen@redhat.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, 9 Mar 2009 21:31:35 +0530 [thread overview]
Message-ID: <20090309160135.GA30654@skywalker> (raw)
In-Reply-To: <20090309113619.GH5578@mit.edu>
On Mon, Mar 09, 2009 at 07:36:19AM -0400, 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
With depth 3 we would have path->p_depth = 2 and with middle
index block would have eh->eh_depth = 1 and depth variable also
will be having value 1. (also path->p_depth - depth)
> deep-tree-2.img.gz contains an extent tree of depth 4....
>
So what is the logical block number with which you trying to allocate
blocks in deep-tree-2.img.gz
-aneesh
next prev parent reply other threads:[~2009-03-09 16:01 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 [this message]
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=20090309160135.GA30654@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=ddi@dubex.dk \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--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).