From: NeilBrown <neilb@suse.de>
To: "Labun, Marcin" <Marcin.Labun@intel.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"Williams, Dan J" <dan.j.williams@intel.com>
Subject: Re: [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata
Date: Mon, 31 Oct 2011 11:31:51 +1100 [thread overview]
Message-ID: <20111031113151.64f566b1@notabene.brown> (raw)
In-Reply-To: <F9123E44003394499FDD2B17C60621D4043755@IRSMSX101.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1846 bytes --]
On Fri, 28 Oct 2011 14:46:57 +0000 "Labun, Marcin" <Marcin.Labun@intel.com>
wrote:
> Hi Neil,
> Please review modified patch in response for your comments.
> I have introduced two flags, one for activation blocking, second for container wide reshapes
> Blocking:
> - some arrays in container are blocked, the others can be activated and reshaped,
> - some arrays are blocked, others can be activated but container wide reshaped is blocked for all.
>
> Thanks,
> Marcin Labun
Thanks. This looks mostly OK.
I have applied it - with a number of formatting improvements and the removal
for a debugging printf :-)
However this bit looks wrong:
> +/*
> + * helper routine to check metadata reshape avalability
> + * 1. Do not "grow" arrays with volume activation blocked
> + * 2. do not reshape containers with container reshape blocked
> + *
> + * IN:
> + * subarray - array name or NULL for container wide reshape
> + * content - md device info from container_content
> + * OUT:
> + * 0 - block reshape
> + */
> +static int check_reshape(char *subarray, struct mdinfo *content)
> +{
> + char *ep;
> + unsigned int idx;
> + printf("subarray: %s\n", subarray);
> +
> +
> + if (!subarray) {
> + if (content->array.state & (1<<MD_SB_BLOCK_CONTAINER_RESHAPE))
> + return 0;
> + }
> + else {
> + /* do not "grow" arrays with volume activation blocked */
> + idx = strtoul(subarray, &ep, 10);
> + if ((*ep == '\0') && (content->container_member == (int) idx) &&
> + (content->array.state & (1<<MD_SB_BLOCK_VOLUME)))
> + return 0;
> + }
> +
> + return 1;
> +}
Grow.c shouldn't be doing a 'strtoul' here. The subarray string belongs to
the metadata handler, mdadm core code shouldn't interpret it at all.
What exactly is the point of that bit of code?
Thanks,
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2011-10-31 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 14:46 [PATCH] kill-subarray: fix, IMSM cannot kill-subarray with unsupported metadata Labun, Marcin
2011-10-31 0:31 ` NeilBrown [this message]
2011-10-31 16:52 ` Labun, Marcin
2011-11-01 4:48 ` NeilBrown
2011-11-03 15:23 ` Labun, Marcin
2011-11-07 1:34 ` NeilBrown
2011-11-10 10:00 ` Labun, Marcin
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=20111031113151.64f566b1@notabene.brown \
--to=neilb@suse.de \
--cc=Marcin.Labun@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).