[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120926033740.GC11468@thunk.org>
Date: Tue, 25 Sep 2012 23:37:40 -0400
From: Theodore Ts'o <tytso@....edu>
To: linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Yongqiang Yang <xiaoqiangnk@...il.com>,
Allison Henderson <achender@...ux.vnet.ibm.com>,
Zheng Liu <wenqing.lz@...bao.com>
Subject: Re: [RFC][PATCH 3/8 v2] ext4: initialize extent status tree
On Wed, Sep 26, 2012 at 11:24:26AM +0800, Zheng Liu wrote:
> > Can you let me know what changes you need to make? If it is to add
> > new features or new sanity checks, does it make sense to simply make
> > it as new commits to existing patch set? Or are there fundamental
> > problems with the current set, that would be better to fix in the
> > current set of commits? (Or is it just minor stylistic/spelling
> > fixes?)
> >
> > Thanks!!
>
> In new patch set, there is three changes as beblow:
>
> 1. add a sanity check in ext4_evict_inode()
> 2. fix a bug in ext4_find_delalloc_range(). This bug is reported by
> xfstest #230 when we enable bigalloc feature.
> 3. Add a new rwlock to protect extent status tree.
>
> So I think that we can only add a sanity check and fix the bigalloc bug,
> and then apply this patch set because the changes are minor. For adding
> a new lock to protect extent status tree, we can add this feature in a
> new patch. If you think it is OK, I can generate a new patch set, do
> some tests using xfstest, and submit it as soon as possible. What's
> your opinion?
Do you think you can get me the patches by the end of the week? If
so, that should work.
Thanks!!
- Ted
--
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
Powered by blists - more mailing lists