From: NeilBrown <neilb@suse.de>
To: Adam Kwolek <adam.kwolek@intel.com>
Cc: linux-raid@vger.kernel.org, dan.j.williams@intel.com,
ed.ciechanowski@intel.com, wojciech.neubauer@intel.com
Subject: Re: [PATCH 1/2] imsm:FIX: change arrays reshape order
Date: Mon, 31 Jan 2011 20:18:00 +1100 [thread overview]
Message-ID: <20110131201800.3a0226de@notabene.brown> (raw)
In-Reply-To: <20110131085922.7551.47081.stgit@gklab-128-013.igk.intel.com>
On Mon, 31 Jan 2011 09:59:22 +0100 Adam Kwolek <adam.kwolek@intel.com> wrote:
> Reshape is started from second array, so it causes imsm incompatibility
> and problems during second array start.
>
> Reshape should be started in arrays metadata order.
>
> Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
> ---
>
> super-intel.c | 9 ++++++++-
> 1 files changed, 8 insertions(+), 1 deletions(-)
>
> diff --git a/super-intel.c b/super-intel.c
> index f578057..8484df6 100644
> --- a/super-intel.c
> +++ b/super-intel.c
> @@ -5848,6 +5848,7 @@ static int apply_reshape_container_disks_update(struct imsm_update_reshape *u,
> int devices_to_reshape = 1;
> struct imsm_super *mpb = super->anchor;
> int ret_val = 0;
> + unsigned int dev_id;
>
> dprintf("imsm: imsm_process_update() for update_reshape\n");
>
> @@ -5877,11 +5878,17 @@ static int apply_reshape_container_disks_update(struct imsm_update_reshape *u,
> " mpb->num_raid_devs = %i\n", mpb->num_raid_devs);
> /* manage changes in volume
> */
> - for (id = super->devlist ; id; id = id->next) {
> + for (dev_id = 0; dev_id < mpb->num_raid_devs; dev_id++) {
> void **sp = *space_list;
> struct imsm_dev *newdev;
> struct imsm_map *newmap, *oldmap;
>
> + for (id = super->devlist ; id; id = id->next) {
> + if (id->index == dev_id)
> + break;
> + }
Could you replace that loop with a call to get_imsm_dev please?
Otherwise, this look good.
Thanks,
NeilBrown
> + if (id == NULL)
> + break;
> if (!sp)
> continue;
> *space_list = *sp;
next prev parent reply other threads:[~2011-01-31 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 8:59 [PATCH 1/2] imsm:FIX: change arrays reshape order Adam Kwolek
2011-01-31 8:59 ` [PATCH 2/2] imsm: Update metadata for second array Adam Kwolek
2011-01-31 9:19 ` NeilBrown
2011-01-31 9:28 ` Kwolek, Adam
2011-01-31 23:23 ` NeilBrown
2011-01-31 9:18 ` NeilBrown [this message]
2011-01-31 9:30 ` [PATCH 1/2] imsm:FIX: change arrays reshape order Kwolek, Adam
2011-01-31 10:10 ` Kwolek, Adam
2011-01-31 23:18 ` NeilBrown
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=20110131201800.3a0226de@notabene.brown \
--to=neilb@suse.de \
--cc=adam.kwolek@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ed.ciechanowski@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=wojciech.neubauer@intel.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;
as well as URLs for NNTP newsgroup(s).