From: Hannes Reinecke <hare@suse.de>
To: James Smart <james.smart@avagotech.com>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 12/14] lpfc: The linux driver does not reinitiate discovery after a failed FLOGI
Date: Mon, 14 Sep 2015 09:40:02 +0200 [thread overview]
Message-ID: <55F679D2.3000804@suse.de> (raw)
In-Reply-To: <55e4bd93.oKGQ536ViqN6PeJn%james.smart@avagotech.com>
On 08/31/2015 10:48 PM, James Smart wrote:
>
> The linux driver does not reinitiate discovery after a failed FLOGI
>
> Forgot to clear FCF Discovery in-progress flag upon FLOGI failures.
> Thus we didn't restart FLOGI.
>
> Signed-off-by: Dick Kennedy <dick.kennedy@avagotech.com>
> Signed-off-by: James Smart <james.smart@avagotech.com>
> ---
> drivers/scsi/lpfc/lpfc_els.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/scsi/lpfc/lpfc_els.c b/drivers/scsi/lpfc/lpfc_els.c
> index 759fa9b..3feeb44 100644
> --- a/drivers/scsi/lpfc/lpfc_els.c
> +++ b/drivers/scsi/lpfc/lpfc_els.c
> @@ -1026,9 +1026,11 @@ lpfc_cmpl_els_flogi(struct lpfc_hba *phba, struct lpfc_iocbq *cmdiocb,
> stop_rr_fcf_flogi:
> /* FLOGI failure */
> lpfc_printf_vlog(vport, KERN_ERR, LOG_ELS,
> - "2858 FLOGI failure Status:x%x/x%x TMO:x%x\n",
> + "2858 FLOGI failure Status:x%x/x%x TMO:x%x "
> + "Data x%x x%x\n",
> irsp->ulpStatus, irsp->un.ulpWord[4],
> - irsp->ulpTimeout);
> + irsp->ulpTimeout, phba->hba_flag,
> + phba->fcf.fcf_flag);
>
> /* Check for retry */
> if (lpfc_els_retry(phba, cmdiocb, rspiocb))
> @@ -1152,6 +1154,9 @@ stop_rr_fcf_flogi:
> }
>
> flogifail:
> + spin_lock_irq(&phba->hbalock);
> + phba->fcf.fcf_flag &= ~FCF_DISCOVERY;
> + spin_unlock_irq(&phba->hbalock);
> lpfc_nlp_put(ndlp);
>
> if (!lpfc_error_lost_link(irsp)) {
>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
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
prev parent reply other threads:[~2015-09-14 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 20:48 [PATCH 12/14] lpfc: The linux driver does not reinitiate discovery after a failed FLOGI James Smart
2015-09-14 7:40 ` Hannes Reinecke [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=55F679D2.3000804@suse.de \
--to=hare@suse.de \
--cc=james.smart@avagotech.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).