linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Jonathan Brassow <jbrassow@redhat.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 1 of 3] MD RAID10: Prep for DM RAID10 device replacement capability
Date: Wed, 5 Sep 2012 12:03:57 +1000	[thread overview]
Message-ID: <20120905120357.7e7dd316@notabene.brown> (raw)
In-Reply-To: <1345832315.25206.16.camel@f16>

[-- Attachment #1: Type: text/plain, Size: 2242 bytes --]

On Fri, 24 Aug 2012 13:18:35 -0500 Jonathan Brassow <jbrassow@redhat.com>
wrote:

> MD RAID10:  Fix a couple potential kernel panics if RAID10 is used by dm-raid
> 
> When device-mapper uses the RAID10 personality through dm-raid.c, there is no
> 'gendisk' structure in mddev and some sysfs information is also not populated.
> 
> This patch avoids touching those non-existent structures.
> 
> Signed-off-by: Jonathan Brassow <jbrassow@rehdat.com>
> 
> Index: linux-upstream/drivers/md/md.c
> ===================================================================
> --- linux-upstream.orig/drivers/md/md.c
> +++ linux-upstream/drivers/md/md.c
> @@ -2056,8 +2056,14 @@ EXPORT_SYMBOL(md_integrity_register);
>  /* Disable data integrity if non-capable/non-matching disk is being added */
>  void md_integrity_add_rdev(struct md_rdev *rdev, struct mddev *mddev)
>  {
> -	struct blk_integrity *bi_rdev = bdev_get_integrity(rdev->bdev);
> -	struct blk_integrity *bi_mddev = blk_get_integrity(mddev->gendisk);
> +	struct blk_integrity *bi_rdev;
> +	struct blk_integrity *bi_mddev;
> +
> +	if (!mddev->gendisk)
> +		return;
> +
> +	bi_rdev = bdev_get_integrity(rdev->bdev);
> +	bi_mddev = blk_get_integrity(mddev->gendisk);
>  
>  	if (!bi_mddev) /* nothing to do */
>  		return;
> Index: linux-upstream/drivers/md/raid10.c
> ===================================================================
> --- linux-upstream.orig/drivers/md/raid10.c
> +++ linux-upstream/drivers/md/raid10.c
> @@ -1632,7 +1632,7 @@ static int raid10_spare_active(struct md
>  			   && !test_bit(Faulty, &tmp->rdev->flags)
>  			   && !test_and_set_bit(In_sync, &tmp->rdev->flags)) {
>  			count++;
> -			sysfs_notify_dirent(tmp->rdev->sysfs_state);
> +			sysfs_notify_dirent_safe(tmp->rdev->sysfs_state);
>  		}
>  	}
>  	spin_lock_irqsave(&conf->device_lock, flags);
> 


This and the other too all look fine - applied.  Thanks.

While reviewing I noticed:

			if (value > rs->md.raid_disks) {
				rs->ti->error = "Invalid rebuild index given";
				return -EINVAL;
			}

(in the 'rebuild' handling).  That should be  'value >= rs->md.raid_disks'
shouldn't it?
If you agree, please send a patch.

Thanks,
NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2012-09-05  2:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 18:18 [PATCH 1 of 3] MD RAID10: Prep for DM RAID10 device replacement capability Jonathan Brassow
2012-09-05  2:03 ` NeilBrown [this message]
2012-09-05 14:53   ` Brassow Jonathan

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=20120905120357.7e7dd316@notabene.brown \
    --to=neilb@suse.de \
    --cc=jbrassow@redhat.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).