summaryrefslogtreecommitdiffstats
path: root/drivers/message/fusion/mptctl.c
diff options
context:
space:
mode:
authorKashyap, Desai2010-07-26 15:26:21 +0200
committerJames Bottomley2010-07-28 16:07:46 +0200
commitc9de7dc48307395fb71780b567ae8833b080d1c8 (patch)
treeb034f8833d64b640d9ef9e3f61191d06b51e5027 /drivers/message/fusion/mptctl.c
parent[SCSI] ibmvstgt: add __init/__exit macros (diff)
downloadkernel-qcow2-linux-c9de7dc48307395fb71780b567ae8833b080d1c8.tar.gz
kernel-qcow2-linux-c9de7dc48307395fb71780b567ae8833b080d1c8.tar.xz
kernel-qcow2-linux-c9de7dc48307395fb71780b567ae8833b080d1c8.zip
[SCSI] mptfusion: Block Error handling for deleting devices or Device in DMD
Issue description: In multipath topology, when device deletion is in transient state, multipath driver can call blk_flush_queue() as part of path failure. Before device get deleted from OS, Device may go OFFLINE as part of error handling kicked off triggered from multipathing driver. Above condition hits more frequently if device missing delay timer (which is LSI specific firmware parameter) is non zero value. root cause of this issue is Error handling thread is getting kicked off for device which is not really present(in transient state of deleting). This patch has solution for this issue. driver is now using eh_timed_out callback. See below. mptsas_transport_template->eh_timed_out = mptsas_eh_timed_out Using mptsas_eh_timed_out function, driver can decide weather vdevice is under Device missing delay or deleting state. for either of those cases, there is BLK_EH_RESET_TIMER return to scsi mid and error handling thread will not be kicked off for that particular scsi command. Signed-off-by: Kashyap Desai <kashyap.desai@lsi.com> Cc: Stable Tree <stable@kernel.org> Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'drivers/message/fusion/mptctl.c')
0 files changed, 0 insertions, 0 deletions