From: Eryu Guan <eguan@redhat.com>
To: fdmanana@kernel.org
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] fstests: btrfs regression test for fsync after extent cloning
Date: Mon, 7 Sep 2015 18:35:43 +0800 [thread overview]
Message-ID: <20150907103543.GE18060@dhcp-13-216.nay.redhat.com> (raw)
In-Reply-To: <1439979128-14169-1-git-send-email-fdmanana@kernel.org>
On Wed, Aug 19, 2015 at 11:12:08AM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> Test that if we fsync a file that got one extent partially cloned into a
> lower file offset, after a power failure our file has the same content it
> had before the power failure and after the extent cloning operation.
>
> This test is motivated by an issue found in btrfs that is fixed by the
> linux kernel patch titled:
>
> "Btrfs: fix file read corruption after extent cloning and fsync"
>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
Looks good to me.
Reviewed-by: Eryu Guan <eguan@redhat.com>
prev parent reply other threads:[~2015-09-07 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 10:12 [PATCH] fstests: btrfs regression test for fsync after extent cloning fdmanana
2015-09-07 10:35 ` 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=20150907103543.GE18060@dhcp-13-216.nay.redhat.com \
--to=eguan@redhat.com \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/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).