From: Anand Jain <anand.jain@oracle.com>
To: Josef Bacik <josef@toxicpanda.com>,
fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
kernel-team@fb.com
Subject: Re: [PATCH 1/3] fstests: check btrfs profile configs before allowing raid56
Date: Wed, 20 Mar 2024 18:01:14 +0530 [thread overview]
Message-ID: <343344c4-7a12-4e58-84b9-6b8a7ef51294@oracle.com> (raw)
In-Reply-To: <65177ca9d943c043f88d8ea034d1e625af3d0e58.1710867187.git.josef@toxicpanda.com>
On 3/19/24 22:25, Josef Bacik wrote:
> For some of our tests we have
>
> _require_btrfs_fs_feature raid56
>
> to make sure the raid56 support is loaded in the kernel. However this
> isn't the only limiting factor, we can have only zoned devices which we
> already check for, but we could also have BTRFS_PROFILE_CONFIGS set
> without raid5 or raid6 as an option. Fix this by simply checking the
> profile as appropriate and skip running the test if we're missing raid5
> or raid6 in our profile settings.
>
> Signed-off-by: Josef Bacik <josef@toxicpanda.com>
> ---
> common/btrfs | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/common/btrfs b/common/btrfs
> index b0f7f095..d9b01a48 100644
> --- a/common/btrfs
> +++ b/common/btrfs
> @@ -111,8 +111,12 @@ _require_btrfs_fs_feature()
> _notrun "Feature $feat not supported by the available btrfs version"
>
> if [ $feat = "raid56" ]; then
> - # Zoned btrfs only supports SINGLE profile
> - _require_non_zoned_device "${SCRATCH_DEV}"
Don't we still need to exclude the zoned device from the
RAID56 test cases?
> + # Make sure it's in our supported configs as well
> + _btrfs_get_profile_configs
> + if [[ ! "${_btrfs_profile_configs[@]}" =~ "raid5" ]] ||
> + [[ ! "${_btrfs_profile_configs[@]}" =~ "raid6" ]]; then
> + _notrun "raid56 excluded from profile configs"
> + fi
> fi
> }
>
Thanks, Anand
next prev parent reply other threads:[~2024-03-20 12:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-19 16:55 [PATCH 0/3] fstests: various RAID56 related fixes for btrfs Josef Bacik
2024-03-19 16:55 ` [PATCH 1/3] fstests: check btrfs profile configs before allowing raid56 Josef Bacik
2024-03-19 20:59 ` Christoph Hellwig
2024-03-20 14:40 ` Josef Bacik
2024-03-21 21:37 ` Christoph Hellwig
2024-03-20 12:31 ` Anand Jain [this message]
2024-03-20 14:41 ` Josef Bacik
2024-03-19 16:55 ` [PATCH 2/3] fstests: btrfs/195: skip raid setups not in the profile configs Josef Bacik
2024-03-24 14:25 ` Anand Jain
2024-03-19 16:55 ` [PATCH 3/3] fstests: add _require_btrfs_fs_feature raid56 to a few tests Josef Bacik
2024-03-21 5:55 ` Naohiro Aota
2024-03-24 14:16 ` Anand Jain
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=343344c4-7a12-4e58-84b9-6b8a7ef51294@oracle.com \
--to=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--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