From: Dave Chinner <david@fromorbit.com>
To: Filipe David Borba Manana <fdmanana@gmail.com>
Cc: xfs@oss.sgi.com, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3] xfstests: add regression test for btrfs incremental send
Date: Mon, 17 Feb 2014 12:19:29 +1100 [thread overview]
Message-ID: <20140217011929.GA13997@dastard> (raw)
In-Reply-To: <1392596438-6509-1-git-send-email-fdmanana@gmail.com>
On Mon, Feb 17, 2014 at 12:20:38AM +0000, Filipe David Borba Manana wrote:
> Test for a btrfs incremental send issue where we end up sending a
> wrong section of data from a file extent if the corresponding file
> extent is compressed and the respective file extent item has a non
> zero data offset.
>
> Fixed by the following linux kernel btrfs patch:
>
> Btrfs: use right clone root offset for compressed extents
>
> Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com>
> ---
>
> V2: Made the test more reliable. Now it doesn't depend anymore of btrfs'
> hole punch implementation leaving hole file extent items when we punch
> beyond the file's current size.
> V3: Filter xfs_io output and make less use of the run_check function, as
> suggested by Dave Chinner.
Awesome. Thanks for the quick turn around.
> common/rc | 5 +++
> tests/btrfs/040 | 119 +++++++++++++++++++++++++++++++++++++++++++++++++++
> tests/btrfs/040.out | 9 ++++
> tests/btrfs/group | 1 +
> 4 files changed, 134 insertions(+)
> create mode 100755 tests/btrfs/040
> create mode 100644 tests/btrfs/040.out
>
> diff --git a/common/rc b/common/rc
> index e91568b..27be009 100644
> --- a/common/rc
> +++ b/common/rc
> @@ -2207,6 +2207,11 @@ run_check()
> "$@" >> $seqres.full 2>&1 || _fail "failed: '$@'"
> }
>
> +_run_btrfs_util_prog()
> +{
> + run_check $BTRFS_UTIL_PROG $*
> +}
Can you do a cleanup of all the other btrfs tests that can use this?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2014-02-17 1:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 20:08 [PATCH] xfstests: add regression test for btrfs incremental send Filipe David Borba Manana
2014-02-15 15:36 ` [PATCH v2] " Filipe David Borba Manana
2014-02-16 23:08 ` Dave Chinner
2014-02-16 23:43 ` Filipe David Manana
2014-02-17 1:17 ` Dave Chinner
2014-02-17 1:40 ` Filipe David Manana
2014-02-17 0:20 ` [PATCH v3] " Filipe David Borba Manana
2014-02-17 1:19 ` Dave Chinner [this message]
2014-02-17 1:42 ` Filipe David Manana
[not found] ` <CAL3q7H4JLbMS+JL4h4du60S1vKFtvceP-Mx-e=0v4nTBwjkATA@mail.gmail.com>
2014-02-17 1:44 ` [PATCH] " Dave Chinner
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=20140217011929.GA13997@dastard \
--to=david@fromorbit.com \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=xfs@oss.sgi.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).