From: fdmanana@kernel.org
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: [PATCH 0/4] fstests/btrfs: add a test case for send v2 and an update
Date: Mon, 28 Nov 2022 12:07:20 +0000 [thread overview]
Message-ID: <cover.1669636339.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
This adds a test case specific for send v2 with some preparatory work in
order to allow for that. Support for v2 send streams was added in
btrfs-progs v5.19 and the kernel support introduced with kernel 6.0.
More send v2 specific tests will be added later.
Filipe Manana (4):
btrfs: add a _require_btrfs_send_v2 helper
common: make _filter_fiemap_flags optionally print the encoded flag
btrfs/280: also verify that fiemap reports extents as encoded
btrfs: test a case with compressed send stream and a shared extent
common/btrfs | 14 +++++++
common/punch | 40 ++++++++++++++++++--
tests/btrfs/280 | 4 +-
tests/btrfs/280.out | 12 +++---
tests/btrfs/281 | 89 +++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/281.out | 17 +++++++++
6 files changed, 164 insertions(+), 12 deletions(-)
create mode 100755 tests/btrfs/281
create mode 100644 tests/btrfs/281.out
--
2.35.1
next reply other threads:[~2022-11-28 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 12:07 fdmanana [this message]
2022-11-28 12:07 ` [PATCH 1/4] btrfs: add a _require_btrfs_send_v2 helper fdmanana
2022-11-28 12:07 ` [PATCH 2/4] common: make _filter_fiemap_flags optionally print the encoded flag fdmanana
2022-11-28 12:07 ` [PATCH 3/4] btrfs/280: also verify that fiemap reports extents as encoded fdmanana
2022-11-28 12:07 ` [PATCH 4/4] btrfs: test a case with compressed send stream and a shared extent fdmanana
2022-11-28 16:05 ` [PATCH 0/4] fstests/btrfs: add a test case for send v2 and an update Josef Bacik
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=cover.1669636339.git.fdmanana@suse.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.