public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi_scan.c : add missing interim SDEV_DEL state if slave_alloc fails
Date: Tue, 27 Jan 2009 16:27:31 +0000	[thread overview]
Message-ID: <1233073651.3231.49.camel@localhost.localdomain> (raw)
In-Reply-To: <1233070798.22506.5.camel@ogier>

On Tue, 2009-01-27 at 10:39 -0500, James Smart wrote:
> We were running i/o and performing a bunch of hba resets in a loop.
> This forces a lot of target removes and rescans. Since the resets
> are occuring during scan it's causing the scan i/o to timeout or fail,
> invoking error recovery, etc.  We end up getting a nasty crash
> in scsi_scan.c due to references to old sdevs that had some
> lingering references that kept them around.
> 
> Fix by setting device state to SDEV_DEL if the LLD's slave_alloc
> fails. This will fail reference taking in subsequent teardown/scan paths.
> 
> -- james s
> 
> 
>  Signed-off-by: James Smart <james.smart@emulex.com>
> 
>  ---
> 
>  scsi_scan.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> 
> diff -upNr a/drivers/scsi/scsi_scan.c b/drivers/scsi/scsi_scan.c
> --- a/drivers/scsi/scsi_scan.c	2009-01-27 09:44:31.000000000 -0500
> +++ b/drivers/scsi/scsi_scan.c	2009-01-27 10:12:04.000000000 -0500
> @@ -310,6 +310,7 @@ static struct scsi_device *scsi_alloc_sd
>  			 */
>  			if (ret == -ENXIO)
>  				display_failure_msg = 0;
> +			scsi_device_set_state(sdev, SDEV_DEL);

A minor nit (since we only have one user of out_device_destroy) is that
the state setting should be done in the out_device_destroy: branch

James



      reply	other threads:[~2009-01-27 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 15:39 [PATCH] scsi_scan.c : add missing interim SDEV_DEL state if slave_alloc fails James Smart
2009-01-27 16:27 ` James Bottomley [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=1233073651.3231.49.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=James.Smart@Emulex.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