From: fdmanana@kernel.org
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: [PATCH 0/3] btrfs: add couple tests to check fiemap correctly reports extent sharedness
Date: Mon, 31 Oct 2022 11:11:18 +0000 [thread overview]
Message-ID: <cover.1667214081.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
This adds two new btrfs specific tests to verify fiemap correctly reports
extent sharedness in a couple of scenarios recently fixed in kernel 6.1-rc2.
More details on the test files.
Filipe Manana (3):
common/punch: fix flags printing for filter _filter_fiemap_flags
btrfs: test that fiemap reports extent as not shared after deleting file
btrfs: test fiemap reports extent as not shared after COWing it in snapshot
common/punch | 2 ++
tests/btrfs/279 | 82 +++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/279.out | 39 +++++++++++++++++++++
tests/btrfs/280 | 64 +++++++++++++++++++++++++++++++++++
tests/btrfs/280.out | 21 ++++++++++++
5 files changed, 208 insertions(+)
create mode 100755 tests/btrfs/279
create mode 100644 tests/btrfs/279.out
create mode 100755 tests/btrfs/280
create mode 100644 tests/btrfs/280.out
--
2.35.1
next reply other threads:[~2022-10-31 11:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 11:11 fdmanana [this message]
2022-10-31 11:11 ` [PATCH 1/3] common/punch: fix flags printing for filter _filter_fiemap_flags fdmanana
2022-10-31 16:23 ` Zorro Lang
2022-10-31 11:11 ` [PATCH 2/3] btrfs: test that fiemap reports extent as not shared after deleting file fdmanana
2022-10-31 16:41 ` Zorro Lang
2022-10-31 16:51 ` Filipe Manana
2022-11-01 5:10 ` Zorro Lang
2022-10-31 11:11 ` [PATCH 3/3] btrfs: test fiemap reports extent as not shared after COWing it in snapshot fdmanana
2022-11-01 5:22 ` Zorro Lang
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.1667214081.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.