From: James Smart <jsmart2021@gmail.com>
To: linux-scsi@vger.kernel.org
Cc: James Smart <jsmart2021@gmail.com>, Justin Tee <justin.tee@broadcom.com>
Subject: [PATCH 1/7] lpfc: Fix unsolicited FLOGI receive handling during PT2PT discovery
Date: Thu, 18 Aug 2022 18:17:30 -0700 [thread overview]
Message-ID: <20220819011736.14141-2-jsmart2021@gmail.com> (raw)
In-Reply-To: <20220819011736.14141-1-jsmart2021@gmail.com>
During a stress offline/online test in PT2PT topology, target
rediscovery can fail with a specific target vendor array.
When the HBA transitions to online mode it is possible to receive an
unsolicited FLOGI before processing the Link Up event. The received
FLOGI will set the defer_flogi_acc_flag, which instructs the driver
to wait until it transmits its own FLOGI before ACKing the received
FLOGI. In this failure scenario, the link up processing clears
the set defer_flogi_acc_flag before we have sent out the FLOGI.
As the target has the higher WWPN and is responsible for sending
the PLOGI, the target is stuck waiting for its FLOGI_ACC that the
driver will never send.
Remove the clear of defer_flogi_acc_flag from Link Up event
processing. In this stress test case, the defer_flogi_acc_flag is
cleared during the Link Down event processing anyways.
Co-developed-by: Justin Tee <justin.tee@broadcom.com>
Signed-off-by: Justin Tee <justin.tee@broadcom.com>
Signed-off-by: James Smart <jsmart2021@gmail.com>
---
drivers/scsi/lpfc/lpfc_hbadisc.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/scsi/lpfc/lpfc_hbadisc.c b/drivers/scsi/lpfc/lpfc_hbadisc.c
index 2645def612e6..36090e21bb10 100644
--- a/drivers/scsi/lpfc/lpfc_hbadisc.c
+++ b/drivers/scsi/lpfc/lpfc_hbadisc.c
@@ -1392,7 +1392,6 @@ lpfc_linkup(struct lpfc_hba *phba)
/* reinitialize initial HBA flag */
phba->hba_flag &= ~(HBA_FLOGI_ISSUED | HBA_RHBA_CMPL);
- phba->defer_flogi_acc_flag = false;
return 0;
}
--
2.26.2
next prev parent reply other threads:[~2022-08-19 1:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 1:17 [PATCH 0/7] lpfc: Update lpfc to revision 14.2.0.6 James Smart
2022-08-19 1:17 ` James Smart [this message]
2022-08-19 1:17 ` [PATCH 2/7] lpfc: Fix null ndlp ptr dereference in abnormal exit path for GFT_ID James Smart
2022-08-19 1:17 ` [PATCH 3/7] lpfc: Rework MIB Rx Monitor debug info logic James Smart
2022-08-19 1:17 ` [PATCH 4/7] lpfc: Add warning notification period to CMF_SYNC_WQE James Smart
2022-08-19 1:17 ` [PATCH 5/7] lpfc: Remove SANDiags related code James Smart
2022-08-19 1:17 ` [PATCH 6/7] lpfc: Update lpfc version to 14.2.0.6 James Smart
2022-08-19 1:17 ` [PATCH 7/7] lpfc: Copyright updates for 14.2.0.6 patches James Smart
2022-08-23 3:51 ` [PATCH 0/7] lpfc: Update lpfc to revision 14.2.0.6 Martin K. Petersen
2022-09-01 5:12 ` Martin K. Petersen
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=20220819011736.14141-2-jsmart2021@gmail.com \
--to=jsmart2021@gmail.com \
--cc=justin.tee@broadcom.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