summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorJames Smart <jsmart2021@gmail.com>2018-11-29 16:09:35 -0800
committerMartin K. Petersen <martin.petersen@oracle.com>2018-12-07 22:35:32 -0500
commit287aba2592870fa5b76134b28173b77f1f7a4492 (patch)
tree23ce42e20e958b3f0d705d254b8970bd969f1cd3 /README
parent92ea83a878c68f709a172dd0125582b311d4d0d0 (diff)
downloadlinux-stable-287aba2592870fa5b76134b28173b77f1f7a4492.tar.gz
linux-stable-287aba2592870fa5b76134b28173b77f1f7a4492.tar.bz2
linux-stable-287aba2592870fa5b76134b28173b77f1f7a4492.zip
scsi: lpfc: ls_rjt erroneus FLOGIs
In some link initialization sequences, the fw generates an erroneous FLOGI payload to the driver without an intervening link bounce. The driver, when it sees a 2nd FLOGI without an intervening link bounce, automatically performs a link bounce. In this, the link bounce causes the situate to repeat and in a nasty loop of link bounces. Resolve the issue by validating the FLOGI payload. The erroneous FLOGI will contain VVL signatures that are not normal. When the driver sees these, it will simply reject the flogi rather than bouncing the link. The reject is consumed within the firmware. Signed-off-by: Dick Kennedy <dick.kennedy@broadcom.com> Signed-off-by: James Smart <jsmart2021@gmail.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions