From: "Darrick J. Wong" <djwong@kernel.org>
To: fdmanana@kernel.org
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
zlang@redhat.com, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH 2/3] fstests: add missing require of xfs_io fiemap command to some tests
Date: Tue, 11 Oct 2022 10:38:43 -0700 [thread overview]
Message-ID: <Y0WqI0D3SAZYzcBM@magnolia> (raw)
In-Reply-To: <f10f9fb7fe2ba35d651150f891aec3d996731a96.1665150613.git.fdmanana@suse.com>
On Fri, Oct 07, 2022 at 02:53:35PM +0100, fdmanana@kernel.org wrote:
> From: Filipe Manana <fdmanana@suse.com>
>
> btrfs/257, btrfs/258, btrfs/259 and xfs/443 use the fiemap command of
> xfs_io but don't do a '_require_xfs_io_command "fiemap"'. So add the
> missing requirement.
>
> Signed-off-by: Filipe Manana <fdmanana@suse.com>
Yep
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
--D
> ---
> tests/btrfs/257 | 1 +
> tests/btrfs/258 | 1 +
> tests/btrfs/259 | 1 +
> tests/xfs/443 | 1 +
> 4 files changed, 4 insertions(+)
>
> diff --git a/tests/btrfs/257 b/tests/btrfs/257
> index 3092495f..87f9e0b2 100755
> --- a/tests/btrfs/257
> +++ b/tests/btrfs/257
> @@ -33,6 +33,7 @@ _require_btrfs_no_compress
> # Needs 4K sectorsize
> _require_btrfs_support_sectorsize 4096
> _require_xfs_io_command "falloc"
> +_require_xfs_io_command "fiemap"
>
> _scratch_mkfs -s 4k >> $seqres.full 2>&1
>
> diff --git a/tests/btrfs/258 b/tests/btrfs/258
> index da073333..be61d039 100755
> --- a/tests/btrfs/258
> +++ b/tests/btrfs/258
> @@ -17,6 +17,7 @@ _begin_fstest auto defrag quick
> # Modify as appropriate.
> _supported_fs generic
> _require_scratch
> +_require_xfs_io_command "fiemap"
>
> # Needs 4K sectorsize, as larger sectorsize can change the file layout.
> _require_btrfs_support_sectorsize 4096
> diff --git a/tests/btrfs/259 b/tests/btrfs/259
> index 92d0b9a6..36f499f9 100755
> --- a/tests/btrfs/259
> +++ b/tests/btrfs/259
> @@ -18,6 +18,7 @@ _begin_fstest auto quick defrag
> # Modify as appropriate.
> _supported_fs btrfs
> _require_scratch
> +_require_xfs_io_command "fiemap"
>
> _scratch_mkfs >> $seqres.full
>
> diff --git a/tests/xfs/443 b/tests/xfs/443
> index f2390bf3..de28b85b 100755
> --- a/tests/xfs/443
> +++ b/tests/xfs/443
> @@ -30,6 +30,7 @@ _require_test_program "punch-alternating"
> _require_xfs_io_command "falloc"
> _require_xfs_io_command "fpunch"
> _require_xfs_io_command "swapext"
> +_require_xfs_io_command "fiemap"
>
> _scratch_mkfs | _filter_mkfs >> $seqres.full 2> $tmp.mkfs
> _scratch_mount
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-10-11 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 13:53 [PATCH 0/3] fstests: add a btrfs fiemap test and fiemap test group fdmanana
2022-10-07 13:53 ` [PATCH 1/3] btrfs: test fiemap on large file with extents shared through a snapshot fdmanana
2022-10-08 3:27 ` Zorro Lang
2022-10-07 13:53 ` [PATCH 2/3] fstests: add missing require of xfs_io fiemap command to some tests fdmanana
2022-10-11 13:56 ` Zorro Lang
2022-10-11 17:38 ` Darrick J. Wong [this message]
2022-10-07 13:53 ` [PATCH 3/3] fstests: add fiemap group fdmanana
2022-10-11 13:55 ` Zorro Lang
2022-10-11 17:45 ` Darrick J. Wong
2022-10-08 3:16 ` [PATCH 0/3] fstests: add a btrfs fiemap test and fiemap test group 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=Y0WqI0D3SAZYzcBM@magnolia \
--to=djwong@kernel.org \
--cc=fdmanana@kernel.org \
--cc=fdmanana@suse.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=zlang@redhat.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