linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] md: check the return of mddev_find()
Date: Tue, 15 May 2012 16:33:53 +1000	[thread overview]
Message-ID: <20120515163353.5ab9c084@notabene.brown> (raw)
In-Reply-To: <1337063200-11174-1-git-send-email-yuanhan.liu@linux.intel.com>

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

On Tue, 15 May 2012 14:26:40 +0800 Yuanhan Liu <yuanhan.liu@linux.intel.com>
wrote:

> Check the return of mddev_find(), since it may fail due to out of
> memeory or out of usable minor number.
> 
> The reason I chose -ENODEV instead of -ENOMEM or something else is
> md_alloc() function chose that ;)
> 
> Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
> ---
>  drivers/md/md.c |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/md/md.c b/drivers/md/md.c
> index 477eb2e..0bd44e3 100644
> --- a/drivers/md/md.c
> +++ b/drivers/md/md.c
> @@ -6371,6 +6371,9 @@ static int md_open(struct block_device *bdev, fmode_t mode)
>  	struct mddev *mddev = mddev_find(bdev->bd_dev);
>  	int err;
>  
> +	if (!mddev)
> +		return -ENODEV;
> +
>  	if (mddev->gendisk != bdev->bd_disk) {
>  		/* we are racing with mddev_put which is discarding this
>  		 * bd_disk.

Hi,
 thanks for the patch.

 I'm fairly sure that we won't actually get to md_open unless md_probe has
 succeeded and called add_disk, in which case there *must* be a matching
 mddev.

 However it doesn't hurt and looks safer so I have applied it.

Thanks,
NeilBrown

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

      reply	other threads:[~2012-05-15  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15  6:26 [PATCH] md: check the return of mddev_find() Yuanhan Liu
2012-05-15  6:33 ` NeilBrown [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=20120515163353.5ab9c084@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=yuanhan.liu@linux.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).