All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ewan Milne <emilne@redhat.com>
To: james.smart@emulex.com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] lpfc: correct device removal deadlock after link bounce
Date: Fri, 02 Jan 2015 11:22:04 -0500	[thread overview]
Message-ID: <1420215724.3891.11.camel@localhost.localdomain> (raw)
In-Reply-To: <1419959338.1683.1.camel@myfc17>

On Tue, 2014-12-30 at 12:08 -0500, James Smart wrote:
> This patch, applicable to 8G/4G/2G adapters, adds a call that 
> resumes transmit operations after a link bounce. Without it, targets
> that tried to suspend exchanges after a link bounce (such as tape devices
> using sequence level error recovery) would never resume io operation,
> causing scan failures, and eventually deadlocks if a device removal
> request is made.
> 
> The patches were cut against Christoph's scsi-queue.git,
> branch "drivers-for-3.18".  The driver rev cut against is 10.4.8000.0
> 
> -- james s
> 
> 
> Signed-off-by: James Smart <james.smart@emulex.com>
> Signed-off-by: Dick Kennedy <dick.kennedy@emulex.com>
> ---
>  lpfc_els.c |    9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff -upNr a/drivers/scsi/lpfc/lpfc_els.c b/drivers/scsi/lpfc/lpfc_els.c
> --- a/drivers/scsi/lpfc/lpfc_els.c	2014-12-29 12:48:08.000000000 -0500
> +++ b/drivers/scsi/lpfc/lpfc_els.c	2014-12-30 11:23:04.344426606 -0500
> @@ -2225,6 +2225,15 @@ lpfc_adisc_done(struct lpfc_vport *vport
>  	if ((phba->sli3_options & LPFC_SLI3_NPIV_ENABLED) &&
>  	    !(vport->fc_flag & FC_RSCN_MODE) &&
>  	    (phba->sli_rev < LPFC_SLI_REV4)) {
> +		/* The ADISCs are complete.  Doesn't matter if they
> +		 * succeeded or failed because the ADISC completion
> +		 * routine guarantees to call the state machine and
> +		 * the RPI is either unregistered (failed ADISC response)
> +		 * or the RPI is still valid and the node is marked
> +		 * mapped for a target.  The exchanges should be in the
> +		 * correct state. This code is specific to SLI3.
> +		 */
> +		lpfc_issue_clear_la(phba, vport);
>  		lpfc_issue_reg_vpi(phba, vport);
>  		return;
>  	}
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reviewed-by: Ewan D. Milne <emilne@redhat.com>



  parent reply	other threads:[~2015-01-02 16:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30 17:08 [PATCH] lpfc: correct device removal deadlock after link bounce James Smart
2014-12-30 17:15 ` Laurence Oberman
2015-01-02 16:22 ` Ewan Milne [this message]
2015-01-05 19:26 ` Christoph Hellwig

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=1420215724.3891.11.camel@localhost.localdomain \
    --to=emilne@redhat.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 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.