summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorJames Smart <James.Smart@Emulex.Com>2006-08-17 11:58:04 -0400
committerJames Bottomley <jejb@mulgrave.il.steeleye.com>2006-08-19 13:46:30 -0700
commita90f56847e8df9034c1c05d1157e1b0cd96987fb (patch)
treed0ec40b563855c7100675e800c2a95c711cd376d /scripts
parent33ccf8d1080bdccb4751a92f6da361a6e01b7cc0 (diff)
downloadlinux-a90f56847e8df9034c1c05d1157e1b0cd96987fb.tar.gz
linux-a90f56847e8df9034c1c05d1157e1b0cd96987fb.tar.bz2
linux-a90f56847e8df9034c1c05d1157e1b0cd96987fb.zip
[SCSI] lpfc 8.1.9 : Stall eh handlers if resetting while rport blocked
Stall error handler if attempting resets/aborts while an rport is blocked. This avoids device offline scenarios due to errors in the error handler. Background: Although the transport is using the scsi_timed_out functionality to restart the timeout if the rport is blocked, if the timeout has already fired before the block occurs, the eh handler still runs and can take the device offline. Ultimately, this window cannot be resolved without significant work in the error handler thread. Christoph noted the first level of these issues when he noted the poor error response handling by the error thread. We found, under heavy load and error testing, that time window from when the scsi_times_out() adds the io to the queue to when the scsi_error_handler gets around to servicing it, can be in the several seconds range. In most cases, these test conditions are highly unusual, but possible. As a result, we're stalling the error handler in this race window so that we can avoid the device_offline transitions. Signed-off-by: James Smart <James.Smart@emulex.com> Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions