diff options
| author |   Daniel Wagner <dwagner@suse.de> | 2020-09-08 10:15:16 +0200 |
|---|---|---|
| committer |   Martin K. Petersen <martin.petersen@oracle.com> | 2020-09-09 22:01:44 -0400 |
| commit | 31a3271ff11badc50d6dc0efb4da393e4c3bf388 (patch) | |
| tree | a61cbc57d995e3ebf68cd5dfa5463b08a2f5b5d6 /tools/perf/scripts/python/stackcollapse.py | |
| parent | scsi: qla2xxx: Log calling function name in qla2x00_get_sp_from_handle() (diff) | |
| download | wireguard-linux-31a3271ff11badc50d6dc0efb4da393e4c3bf388.tar.xz wireguard-linux-31a3271ff11badc50d6dc0efb4da393e4c3bf388.zip | |
scsi: qla2xxx: Handle incorrect entry_type entries
It was observed on an ISP8324 16Gb HBA with fw=8.08.203 (d0d5) in a
PowerPC64 machine that pkt->entry_type was MBX_IOCB_TYPE/0x39 with an
sp->type SRB_SCSI_CMD which is invalid and should not be possible.
Reading the entry_type from the crash dump shows the expected value of
STATUS_TYPE/0x03 but the call trace shows that qla24xx_mbx_iocb_entry() is
used.
Add a check to verify for consistency and reset the HBA if an invalid state
is reached. Obviously, this is only a workaround until the real problem is
solved.
Link: https://lore.kernel.org/r/20200908081516.8561-5-dwagner@suse.de
Reviewed-by: Arun Easi <aeasi@marvell.com>
Signed-off-by: Daniel Wagner <dwagner@suse.de>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions