From: Theodore Ts'o <tytso@mit.edu>
To: linux-ext4@vger.kernel.org, Zheng Liu <wenqing.lz@taobao.com>
Subject: Re: [RESEND][PATCH 2/2 v2] ext4: let us fully support punching hole feature in fallocate
Date: Thu, 24 Jan 2013 23:21:22 -0500 [thread overview]
Message-ID: <20130125042122.GG28908@thunk.org> (raw)
In-Reply-To: <20130125035912.GA15806@gmail.com>
On Fri, Jan 25, 2013 at 11:59:12AM +0800, Zheng Liu wrote:
>
> I wonder that maybe we need to submit a patch to let xfstest understand
> that a filesystem supports extents or not because after applied this
> patch indirect-based file in ext4 has supported seek_data/hole and hole
> punching. I usually run xfstest automatically, and every time I need
> to check the result of #255 and #285 manually. That is annoying for me.
I would think the right thing to do is to have xfstests make sure it
understands that fallocate working with FALLOC_FL_PUNCH_HOLE does not
imply that fallocate without the FALLOC_FL_PUNCH_HOLE flag OR'ed in
will work. It should test for support for preallocation and hole
punching separately, and do tests accordingly.
That way we don't have to add explicit ext4 knowledge/logic to
xfstests. (Maybe in the future there will be some other file system
which supports punch hole but not preallocate, and it might not be
based on whether or not the file is using ext4 extents or not.)
Cheers,
- Ted
next prev parent reply other threads:[~2013-01-25 4:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 7:16 [RESEND][PATCH 1/2 v2] ext4: add indirect punching hole support Zheng Liu
2013-01-18 7:16 ` [RESEND][PATCH 2/2 v2] ext4: let us fully support punching hole feature in fallocate Zheng Liu
2013-01-25 3:32 ` Theodore Ts'o
2013-01-25 3:59 ` Zheng Liu
2013-01-25 4:21 ` Theodore Ts'o [this message]
2013-01-26 0:47 ` Dave Chinner
2013-01-28 5:04 ` Zheng Liu
2013-01-28 4:57 ` Theodore Ts'o
2013-01-28 5:16 ` Zheng Liu
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=20130125042122.GG28908@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=wenqing.lz@taobao.com \
/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).