From: Eryu Guan <guaneryu@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Ted Tso <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0/2 v2] ext4: Fix SEEK_HOLE implementation
Date: Wed, 17 May 2017 20:40:55 +0800 [thread overview]
Message-ID: <20170517124055.GI1946@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20170517120739.2529-1-jack@suse.cz>
Hi Jan,
On Wed, May 17, 2017 at 02:07:37PM +0200, Jan Kara wrote:
> Hello,
>
> here is second revision of the patch set to fix ext4 SEEK_HOLE implementation.
> For more details see changelog of the first patch.
>
> Changes since v1:
> * Fix some more buggy cases
> * Fix range check
> * Simplify the code
This patchset fails generic/285 on sub-page block size ext4 too, again
failres were from subtest 7 and 8, as where xfs failed.
Thanks,
Eryu
prev parent reply other threads:[~2017-05-17 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 12:07 [PATCH 0/2 v2] ext4: Fix SEEK_HOLE implementation Jan Kara
2017-05-17 12:07 ` [PATCH 1/2] ext4: Fix SEEK_HOLE Jan Kara
2017-05-17 12:07 ` [PATCH 2/2] ext4: Fix off-by-in in loop termination in ext4_find_unwritten_pgoff() Jan Kara
2017-05-17 12:40 ` Eryu Guan [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=20170517124055.GI1946@eguan.usersys.redhat.com \
--to=guaneryu@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--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