From: Mike Snitzer <snitzer@redhat.com>
To: Andy Whitcroft <apw@canonical.com>
Cc: Alasdair Kergon <agk@redhat.com>,
Heinz Mauelshagen <heinzm@redhat.com>,
linux-kernel@vger.kernel.org, dm-devel@redhat.com
Subject: Re: [PATCH 1/1] dm raid: fix compat_features validation
Date: Tue, 11 Oct 2016 10:46:42 -0400 [thread overview]
Message-ID: <20161011144642.GA24888@redhat.com> (raw)
In-Reply-To: <20161011142835.11620-1-apw@canonical.com>
On Tue, Oct 11 2016 at 10:28am -0400,
Andy Whitcroft <apw@canonical.com> wrote:
> In commit 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.
>
> Check compat_features for any valid combinations.
>
> Fixes: ecbfb9f118bce4 ("dm raid: add raid level takeover support")
> BugLink: http://bugs.launchpad.net/bugs/1631298
> Signed-off-by: Andy Whitcroft <apw@canonical.com>
> ---
> drivers/md/dm-raid.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> It very much looks like these are intended to be optional extended feature
> flags. That we should be accepting any valid flag and rejecting any bit
> not in that set. We should however not be ensuring that specific bits
> are actually set. Certainly as things stand raid sets built on previous
> kernel versions cannot be assembled.
Right, your patch looks good to me. But I'll wait for confirmation from
Heinz before I stage your fix.
Thanks,
Mike
next prev parent reply other threads:[~2016-10-11 14:46 UTC|newest]
Thread overview: 12+ 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 14:46 ` Mike Snitzer [this message]
2016-10-11 15:04 ` [dm-devel] " Heinz Mauelshagen
2016-10-11 15:38 ` Andy Whitcroft
2016-10-11 15:38 ` [dm-devel] " Andy Whitcroft
2016-10-11 15:44 ` Heinz Mauelshagen
2016-10-11 16:21 ` [PATCH 1/1 V2] " Andy Whitcroft
2016-10-11 16:21 ` Andy Whitcroft
2016-10-11 16:53 ` Heinz Mauelshagen
2016-10-11 17:44 ` [PATCH 1/1] " Mike Snitzer
2016-10-11 17:44 ` 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=20161011144642.GA24888@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=apw@canonical.com \
--cc=dm-devel@redhat.com \
--cc=heinzm@redhat.com \
--cc=linux-kernel@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.