[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1106241035490.5123@dhcp-27-109.brq.redhat.com>
Date: Fri, 24 Jun 2011 10:39:31 +0200 (CEST)
From: Lukas Czerner <lczerner@...hat.com>
To: Robin Dong <hao.bigrat@...il.com>
cc: Yongqiang Yang <xiaoqiangnk@...il.com>,
Eric Sandeen <sandeen@...hat.com>, linux-ext4@...r.kernel.org,
Robin Dong <sanbai@...bao.com>
Subject: Re: [PATCH v2] ext4: avoid eh_entries overflow before insert
extent_idx
On Fri, 24 Jun 2011, Robin Dong wrote:
> 2011/6/24 Yongqiang Yang <xiaoqiangnk@...il.com>:
> > On Thu, Jun 23, 2011 at 10:57 PM, Eric Sandeen <sandeen@...hat.com> wrote:
> >> On 6/23/11 3:47 AM, Robin Dong wrote:
> >>> If eh_entries is equal to (or greater than) eh_max, the operation of
> >>> inserting new extent_idx will make number of entries overflow.
> >>> So check eh_entries before inserting the new extent_idx.
> >>
> >> Do you have any testcase you can share which shows this bug?
> > I am not sure if Robin has any test case.
> >
> > According to code, I think there is no bug case. Because this
> > function is called by ext4_ext_split() and ext4_ext_split() is called
> > only if the index block has free space.
> >
> > I think the right logic should be as this patch shows, that is, we
> > should lookup the capacity before insertion.
>
> Exactly! :-)
Hi Robin, this is the reason why I asked you to provide better commit
description with better reasoning for this change. Since it is not
immediately clear from the patch itself why you did the change, it saves
time for everyone (just FYI for the next time:).
Thanks!
-Lukas
Powered by blists - more mailing lists