linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: James Bottomley <James.Bottomley@suse.de>
Cc: linux-scsi@vger.kernel.org, Eddie Williams <eddie.williams@steeleye.com>
Subject: Re: [PATCH for-2.6.39] [SCSI] scsi_dh_emc: fix panic when handling multiple path failures
Date: Wed, 23 Mar 2011 17:58:26 -0400	[thread overview]
Message-ID: <20110323215826.GA3433@redhat.com> (raw)
In-Reply-To: <20110321231657.GA12902@redhat.com>

On Mon, Mar 21 2011 at  7:16pm -0400,
Mike Snitzer <snitzer@redhat.com> wrote:

> > It's a bug fix: of course it can.
> 
> Right, so given scsi_dh_activate()'s {get,put}_device() that wraps the
> call to scsi_dh->activate (aka clariion_activate) I'm not seeing how
> accessing sdev->sdev_gendev (via sdev_printk) could result in a panic.
> So I'll need to dig deeper (hopefully with Eddie's assistance)...

Hi James,

I checked with Eddie and the sdev_printk() panic he saw no longer occurs
when commit db422318 is in place.  But he also tested with the patch I
provided below.

I still feel this fix is needed and would like to get your feedback on
this (relative to 2.6.39):

> But now that I look at scsi_dh_activate's 'err' path, it would appear
> that we don't drop the reference (put_device) before returning 'err'.  I
> unfotunately had a role in the offending change (commit: db422318)
> getting upstream.  /me ducks
> 
> Looks to me like we need this:
> 
> 
> From: Mike Snitzer <snitzer@redhat.com>
> Subject: [SCSI] scsi_dh: fix reference counting in scsi_dh_activate error path
> 
> Commit db422318cbca55168cf965f655471dbf8be82433 ([SCSI] scsi_dh:
> propagate SCSI device deletion) introduced a regression where the device
> reference is not dropped prior to scsi_dh_activate's early return from
> the error path.
> 
> Signed-off-by: Mike Snitzer <snitzer@redhat.com>
> Cc: stable@kernel.org
> ---
>  drivers/scsi/device_handler/scsi_dh.c |    9 ++++++---
>  1 files changed, 6 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/scsi/device_handler/scsi_dh.c b/drivers/scsi/device_handler/scsi_dh.c
> index 564e6ec..0119b81 100644
> --- a/drivers/scsi/device_handler/scsi_dh.c
> +++ b/drivers/scsi/device_handler/scsi_dh.c
> @@ -394,12 +394,14 @@ int scsi_dh_activate(struct request_queue *q, activate_complete fn, void *data)
>  	unsigned long flags;
>  	struct scsi_device *sdev;
>  	struct scsi_device_handler *scsi_dh = NULL;
> +	struct device *dev = NULL;
>  
>  	spin_lock_irqsave(q->queue_lock, flags);
>  	sdev = q->queuedata;
>  	if (sdev && sdev->scsi_dh_data)
>  		scsi_dh = sdev->scsi_dh_data->scsi_dh;
> -	if (!scsi_dh || !get_device(&sdev->sdev_gendev) ||
> +	dev = get_device(&sdev->sdev_gendev);
> +	if (!scsi_dh || !dev ||
>  	    sdev->sdev_state == SDEV_CANCEL ||
>  	    sdev->sdev_state == SDEV_DEL)
>  		err = SCSI_DH_NOSYS;
> @@ -410,12 +412,13 @@ int scsi_dh_activate(struct request_queue *q, activate_complete fn, void *data)
>  	if (err) {
>  		if (fn)
>  			fn(data, err);
> -		return err;
> +		goto out;
>  	}
>  
>  	if (scsi_dh->activate)
>  		err = scsi_dh->activate(sdev, fn, data);
> -	put_device(&sdev->sdev_gendev);
> +out:
> +	put_device(dev);
>  	return err;
>  }
>  EXPORT_SYMBOL_GPL(scsi_dh_activate);
> 

  parent reply	other threads:[~2011-03-23 21:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 19:57 [PATCH for-2.6.39] [SCSI] scsi_dh_emc: fix panic when handling multiple path failures Mike Snitzer
2011-03-21 20:02 ` James Bottomley
2011-03-21 20:38   ` Mike Snitzer
2011-03-21 20:44     ` James Bottomley
2011-03-21 23:16       ` Mike Snitzer
     [not found]         ` <AANLkTimknz6=6CeURQD_ZB+9DD9W20-rfktjp75nsZrW@mail.gmail.com>
2011-03-22  2:36           ` Eddie Williams
2011-03-23 21:58         ` Mike Snitzer [this message]
2011-03-23 22:03           ` James Bottomley
2011-03-23 23:02             ` Mike Snitzer

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=20110323215826.GA3433@redhat.com \
    --to=snitzer@redhat.com \
    --cc=James.Bottomley@suse.de \
    --cc=eddie.williams@steeleye.com \
    --cc=linux-scsi@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).