diff options
| author | James Smart <jsmart2021@gmail.com> | 2018-08-16 16:04:05 -0700 |
|---|---|---|
| committer | Martin K. Petersen <martin.petersen@oracle.com> | 2018-08-27 12:26:10 -0400 |
| commit | 53e13ee087a80e8d4fc95436318436e5c2c1f8c2 (patch) | |
| tree | c8282e6ac5045107df1c1e9ff4b41b5f0afdd6bc /lib/fdt_strerror.c | |
| parent | 9abd9990e9779dc9c548c3599aaca7e3505ab19d (diff) | |
| download | linux-53e13ee087a80e8d4fc95436318436e5c2c1f8c2.tar.gz linux-53e13ee087a80e8d4fc95436318436e5c2c1f8c2.tar.bz2 linux-53e13ee087a80e8d4fc95436318436e5c2c1f8c2.zip | |
scsi: lpfc: Correct MDS diag and nvmet configuration
A recent change added some MDS processing in the lpfc_drain_txq routine
that relies on the fcp_wq being allocated. For nvmet operation the fcp_wq
is not allocated because it can only be an nvme-target. When the original
MDS support was added LS_MDS_LOOPBACK was defined wrong, (0x16) it should
have been 0x10 (decimal value used for hex setting). This incorrect value
allowed MDS_LOOPBACK to be set simultaneously with LS_NPIV_FAB_SUPPORTED,
causing the driver to crash when it accesses the non-existent fcp_wq.
Correct the bad value setting for LS_MDS_LOOPBACK.
Fixes: ae9e28f36a6c ("lpfc: Add MDS Diagnostic support.")
Cc: <stable@vger.kernel.org> # v4.12+
Signed-off-by: Dick Kennedy <dick.kennedy@broadcom.com>
Signed-off-by: James Smart <james.smart@broadcom.com>
Tested-by: Ewan D. Milne <emilne@redhat.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'lib/fdt_strerror.c')
0 files changed, 0 insertions, 0 deletions