From: Heinz Mauelshagen <heinzm@redhat.com>
To: Andy Whitcroft <apw@canonical.com>
Cc: Mike Snitzer <snitzer@redhat.com>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
dm-devel@redhat.com, Shaohua Li <shli@kernel.org>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: [PATCH 1/1 V2] dm raid: fix compat_features validation
Date: Tue, 11 Oct 2016 18:53:48 +0200 [thread overview]
Message-ID: <f8b9807a-1731-24bc-60d2-27657049ab1d@redhat.com> (raw)
In-Reply-To: <20161011162148.hz2ncmbvtmtmzjkz@brain>
Acked-by: Heinz Mauelshagen <heinzm@redhat.com>
On 10/11/2016 06:21 PM, Andy Whitcroft wrote:
> From a30fba068e41214cb0ffcb14e68722482765e0c9 Mon Sep 17 00:00:00 2001
> From: Andy Whitcroft <apw@canonical.com>
> Date: Tue, 11 Oct 2016 15:16:57 +0100
>
> In ecbfb9f118bce4 ("dm raid: add raid level takeover support") a new
> compatible feature flag was added. Validation for these compat_features
> was added but this only passes for new raid mappings with this feature
> flag. This causes previously created raid mappings to be failed at
> import.
Clarification:
to allow for feature checks, the compat_features member was
in the dm-raid superblock from the beginning (so before ecbfb9f118bce4).
It got renamed from features to compat_features because incompat_features
got introduced with that commit together with the problematic check
of compat_features you thankfully found.
>
> Check compat_features for the only valid combination.
>
> Fixes: ecbfb9f118bce4 ("dm raid: add raid level takeover support")
> Signed-off-by: Andy Whitcroft <apw@canonical.com>
> ---
> drivers/md/dm-raid.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> V2: simplify checks as per maintainer.
>
> diff --git a/drivers/md/dm-raid.c b/drivers/md/dm-raid.c
> index 8abde6b..2a39700 100644
> --- a/drivers/md/dm-raid.c
> +++ b/drivers/md/dm-raid.c
> @@ -2258,7 +2258,8 @@ static int super_validate(struct raid_set *rs, struct md_rdev *rdev)
> if (!mddev->events && super_init_validation(rs, rdev))
> return -EINVAL;
>
> - if (le32_to_cpu(sb->compat_features) != FEATURE_FLAG_SUPPORTS_V190) {
> + if (le32_to_cpu(sb->compat_features) &&
> + le32_to_cpu(sb->compat_features) != FEATURE_FLAG_SUPPORTS_V190) {
> rs->ti->error = "Unable to assemble array: Unknown flag(s) in compatible feature flags";
> return -EINVAL;
> }
next prev parent reply other threads:[~2016-10-11 16:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 14:28 [PATCH 1/1] dm raid: fix compat_features validation Andy Whitcroft
2016-10-11 15:04 ` [dm-devel] " Heinz Mauelshagen
2016-10-11 15:38 ` Andy Whitcroft
2016-10-11 15:44 ` [dm-devel] " Heinz Mauelshagen
2016-10-11 16:21 ` [PATCH 1/1 V2] " Andy Whitcroft
2016-10-11 16:53 ` Heinz Mauelshagen [this message]
2016-10-11 17:44 ` [PATCH 1/1] " Mike Snitzer
2016-10-14 17:14 ` Heinz Mauelshagen
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=f8b9807a-1731-24bc-60d2-27657049ab1d@redhat.com \
--to=heinzm@redhat.com \
--cc=agk@redhat.com \
--cc=apw@canonical.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@kernel.org \
--cc=snitzer@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