Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "Kwolek, Adam" <adam.kwolek@intel.com>
To: NeilBrown <neilb@suse.de>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
	"Williams, Dan J" <dan.j.williams@intel.com>,
	"Ciechanowski, Ed" <ed.ciechanowski@intel.com>,
	"Neubauer, Wojciech" <Wojciech.Neubauer@intel.com>
Subject: RE: [PATCH] imsm: FIX: crash during getting map
Date: Thu, 3 Feb 2011 08:21:30 +0000	[thread overview]
Message-ID: <905EDD02F158D948B186911EB64DB3D1770B8137@irsmsx503.ger.corp.intel.com> (raw)
In-Reply-To: <20110203170338.38c28ae3@notabene.brown>

Could you give me branch name were the changes can be visible?

Thanks
Adam


> -----Original Message-----
> From: linux-raid-owner@vger.kernel.org [mailto:linux-raid-
> owner@vger.kernel.org] On Behalf Of NeilBrown
> Sent: Thursday, February 03, 2011 7:04 AM
> To: Kwolek, Adam
> Cc: linux-raid@vger.kernel.org; Williams, Dan J; Ciechanowski, Ed;
> Neubauer, Wojciech
> Subject: Re: [PATCH] imsm: FIX: crash during getting map
> 
> On Tue, 01 Feb 2011 08:57:37 +0100 Adam Kwolek <adam.kwolek@intel.com>
> wrote:
> 
> > When get_imsm_map() is called with second_map parameter == '-1'
> > and array is not in migration state NULL pointer is returned.
> > This is wrong. '-1' means return map as migration record points.
> >
> > '-1' can be passed to get_imsm_map() from imsm_num_data_members().
> > imsm_num_data_members() is called to get current map members based
> > on migr_state information
> >
> > Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
> > ---
> >
> >  super-intel.c |    7 ++++---
> >  1 files changed, 4 insertions(+), 3 deletions(-)
> >
> > diff --git a/super-intel.c b/super-intel.c
> > index 84ab47b..ee0d9c4 100644
> > --- a/super-intel.c
> > +++ b/super-intel.c
> > @@ -567,15 +567,16 @@ struct imsm_map *get_imsm_map(struct imsm_dev
> *dev, int second_map)
> >  {
> >  	struct imsm_map *map = &dev->vol.map[0];
> >
> > -	if (second_map && !dev->vol.migr_state)
> > +	if ((second_map == 1) && !dev->vol.migr_state)
> >  		return NULL;
> > -	else if (second_map) {
> > +	else if ((second_map == 1) ||
> > +		 ((second_map < 0) && (dev->vol.migr_state))) {
> >  		void *ptr = map;
> >
> >  		return ptr + sizeof_imsm_map(map);
> >  	} else
> >  		return map;
> > -
> > +
> >  }
> >
> >  /* return the size of the device.
> 
> Thanks.
> I added some comments and took the opportunity to simplify
> get_imsm_ord_tbl_ent.  See below.
> 
> NeilBrown
> 
> commit 5e7b0330669594ee79201d19ff45a7850fa0f951
> Author: Adam Kwolek <adam.kwolek@intel.com>
> Date:   Thu Feb 3 17:02:39 2011 +1100
> 
>     imsm: FIX: crash during getting map
> 
>     When get_imsm_map() is called with second_map parameter == '-1'
>     and array is not in migration state NULL pointer is returned.
>     This is wrong. '-1' means return map as migration record points.
> 
>     '-1' can be passed to get_imsm_map() from imsm_num_data_members().
>     imsm_num_data_members() is called to get current map members based
>     on migr_state information
> 
>     Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
>     Signed-off-by: NeilBrown <neilb@suse.de>
> 
> diff --git a/super-intel.c b/super-intel.c
> index 84ab47b..4081071 100644
> --- a/super-intel.c
> +++ b/super-intel.c
> @@ -565,17 +565,24 @@ static size_t sizeof_imsm_map(struct imsm_map
> *map)
> 
>  struct imsm_map *get_imsm_map(struct imsm_dev *dev, int second_map)
>  {
> +	/* A device can have 2 maps if it is in the middle of a
> migration.
> +	 * If second_map is:
> +	 *    0   - we return the first map
> +	 *    1   - we return the second map if it exists, else NULL
> +	 *   -1   - we return the second map if it exists, else the first
> +	 */
>  	struct imsm_map *map = &dev->vol.map[0];
> 
> -	if (second_map && !dev->vol.migr_state)
> +	if (second_map == 1 && !dev->vol.migr_state)
>  		return NULL;
> -	else if (second_map) {
> +	else if (second_map == 1 ||
> +		 (second_map < 0 && dev->vol.migr_state)) {
>  		void *ptr = map;
> 
>  		return ptr + sizeof_imsm_map(map);
>  	} else
>  		return map;
> -
> +
>  }
> 
>  /* return the size of the device.
> @@ -654,14 +661,7 @@ static __u32 get_imsm_ord_tbl_ent(struct imsm_dev
> *dev,
>  {
>  	struct imsm_map *map;
> 
> -	if (second_map == -1) {
> -		if (dev->vol.migr_state)
> -			map = get_imsm_map(dev, 1);
> -		else
> -			map = get_imsm_map(dev, 0);
> -	} else {
> -		map = get_imsm_map(dev, second_map);
> -	}
> +	map = get_imsm_map(dev, second_map);
> 
>  	/* top byte identifies disk under rebuild */
>  	return __le32_to_cpu(map->disk_ord_tbl[slot]);
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2011-02-03  8:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01  7:57 [PATCH] imsm: FIX: crash during getting map Adam Kwolek
2011-02-03  6:03 ` NeilBrown
2011-02-03  8:21   ` Kwolek, Adam [this message]

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=905EDD02F158D948B186911EB64DB3D1770B8137@irsmsx503.ger.corp.intel.com \
    --to=adam.kwolek@intel.com \
    --cc=Wojciech.Neubauer@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=ed.ciechanowski@intel.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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