summaryrefslogtreecommitdiffstats
path: root/drivers/scsi/wd33c93.c
diff options
context:
space:
mode:
authorMichael Reed <mdr@sgi.com>2008-03-20 23:32:05 +0100
committerJames Bottomley <James.Bottomley@HansenPartnership.com>2008-04-07 19:19:00 +0200
commit7748369f49d428e558c519ed344d3005d38347b7 (patch)
tree37a8bcdbd147d11bf1d93c2cb2a0ac3404e4b0a2 /drivers/scsi/wd33c93.c
parent[SCSI] qla4xxx: fix scsi command completion, lun reset and target reset code (diff)
downloadlinux-7748369f49d428e558c519ed344d3005d38347b7.tar.xz
linux-7748369f49d428e558c519ed344d3005d38347b7.zip
[SCSI] mptsas: do not use ioc->handle to locate hba portinfo structure
While performing hardware raid reset testing via the raid's client, I noticed that sometimes, following the reset, that there would be more raid targets in the lsscsi output than there actually were raid targets. I tracked this down to the following issue. Fusion cannot always find the mptsas_portinfo structure for the hba because it uses the handle stored in ioc->handle to locate it. The problem is that the firmware can change the handle associated with the hba when h/w raid is reset (via the raid client). When this happens, the driver will allocate another mptsas_portinfo structure and link it into the chain of said structures. This ultimately causes confusion within the driver resulting in targets not being removed when they should be. Eric Moore pointed out that the hba's portinfo structure is always the first structure on the sas_topology list. This patch modifies mptsas.c to access the hba's portinfo structure by taking the first structure on said list. Signed-off-by: Michael Reed <mdr@sgi.com> Acked-by: "Moore, Eric" <Eric.Moore@lsi.com> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
Diffstat (limited to 'drivers/scsi/wd33c93.c')
0 files changed, 0 insertions, 0 deletions