From: Theodore Ts'o <tytso@mit.edu>
To: Ashish Sangwan <ashishsangwan2@gmail.com>
Cc: adilger@dilger.ca, ext4 development <linux-ext4@vger.kernel.org>,
Ashish Sangwan <a.sangwan@samsung.com>,
Namjae Jeon <namjae.jeon@samsung.com>
Subject: Re: [PATCH] ext4: optimize extent selection for block removal in case of hole punch
Date: Sun, 23 Jun 2013 14:43:25 -0400 [thread overview]
Message-ID: <20130623184325.GD16620@thunk.org> (raw)
In-Reply-To: <CAOiN93=8fTSxNOuzQEhrg69FHb2uCNdLWXKObhGPLqaqXX0B4A@mail.gmail.com>
Lukas's patch: "ext4: only zero partial blocks in
ext4_zero_partial_blocks()" appears to address the failures I was
seeing with xfstests 269 and 270, so I'm going to add this patch back
to the ext4 git tree.
Regards,
- Ted
prev parent reply other threads:[~2013-06-23 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 14:39 [PATCH] ext4: optimize extent selection for block removal in case of hole punch ashishsangwan2
2013-06-18 15:40 ` Theodore Ts'o
2013-06-19 13:45 ` Ashish Sangwan
2013-06-19 14:06 ` Theodore Ts'o
2013-06-19 15:44 ` Ashish Sangwan
2013-06-23 18:43 ` Theodore Ts'o [this message]
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=20130623184325.GD16620@thunk.org \
--to=tytso@mit.edu \
--cc=a.sangwan@samsung.com \
--cc=adilger@dilger.ca \
--cc=ashishsangwan2@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=namjae.jeon@samsung.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).