All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Smart <James.Smart@Emulex.Com>
To: Hannes Reinecke <hare@suse.de>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] FC_Transport: Check portstates before invoking target scan
Date: Thu, 14 Jun 2007 07:57:05 -0400	[thread overview]
Message-ID: <46712D11.1010506@emulex.com> (raw)
In-Reply-To: <4670EDCA.5070302@suse.de>

Sounds reasonable...  Only change I'd make is rather than comparing all the
different states, simply compare  (rport->port_state != FC_PORTSTATE_ONLINE)

-- james s

Hannes Reinecke wrote:
> Hi James (& James, too :-),
> 
> scsi_transport_fc.c:fc_user_scan() should check the portstates prior to
> calling scsi_scan_target(). Otherwise we might get a nice oops as the
> rport might already been disconnected from the host by the time we're
> calling scsi_scan_target(). Thus the traversal from the rport to the
> scsi_host in scsi_scan_target() will fail, resulting in a nice Oops.
> Plus it's quite pointless to scan a target if the portstates already
> told us that we can't communicate with it.
> 
> Please apply.
> 
> Cheers,
> 
> Hannes
> 
> 
> ------------------------------------------------------------------------
> 
> scsi_transport_fc: Check portstates before invoking target scan
> 
> When a target scan is initiated from sysfs, we should check the
> portstate prior to invoke scsi_scan_target().
> Otherwise scsi_scan_target() might oops as the rport might already
> been removed from the scsi host and the traversal from the rport to
> the scsi_host in scsi_scan_target() will fail.
> Also the portstate already told us that communication with the target
> has failed, so it's quite pointless to try.
> 
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> 
> diff --git a/drivers/scsi/scsi_transport_fc.c b/drivers/scsi/scsi_transport_fc.c
> index 4953f0d..bd73615 100644
> --- a/drivers/scsi/scsi_transport_fc.c
> +++ b/drivers/scsi/scsi_transport_fc.c
> @@ -1943,6 +1943,12 @@ static int fc_user_scan(struct Scsi_Host
>  		if (rport->scsi_target_id == -1)
>  			continue;
>  
> +		if ((rport->port_state == FC_PORTSTATE_NOTPRESENT) ||
> +		    (rport->port_state == FC_PORTSTATE_UNKNOWN) ||
> +		    (rport->port_state == FC_PORTSTATE_DELETED) ||
> +		    (rport->port_state == FC_PORTSTATE_BLOCKED))
> +			continue;
> +
>  		if ((channel == SCAN_WILD_CARD || channel == rport->channel) &&
>  		    (id == SCAN_WILD_CARD || id == rport->scsi_target_id)) {
>  			scsi_scan_target(&rport->dev, rport->channel,

  reply	other threads:[~2007-06-14 11:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14  7:27 [PATCH] FC_Transport: Check portstates before invoking target scan Hannes Reinecke
2007-06-14 11:57 ` James Smart [this message]
2007-06-14 13:16   ` Hannes Reinecke

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=46712D11.1010506@emulex.com \
    --to=james.smart@emulex.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=hare@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.