aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/scsi/fcoe
diff options
context:
space:
mode:
authorWayne Boyer <wayneb@linux.vnet.ibm.com>2010-06-10 14:46:34 -0700
committerJames Bottomley <James.Bottomley@suse.de>2010-07-27 12:01:42 -0500
commit56115598c571cadd4b465836e1423a452a908c89 (patch)
treee2b37e4e62e6fb1b0d243b2e2d5d5a6b57e2a6fc /drivers/scsi/fcoe
parent82284c09c5dc5c5a5046f3c852f2683dab60109c (diff)
downloadkernel_samsung_smdk4412-56115598c571cadd4b465836e1423a452a908c89.zip
kernel_samsung_smdk4412-56115598c571cadd4b465836e1423a452a908c89.tar.gz
kernel_samsung_smdk4412-56115598c571cadd4b465836e1423a452a908c89.tar.bz2
[SCSI] ipr: move setting of the allow_restart flag for vsets and disks
A problem was found where the call to scsi_add_device() fails intermittently for an adapter. This is caused when __scsi_add_device() returns -ENODEV as a result of not calling scsi_probe_and_add_lun() since the call to scsi_host_scan_allowed() fails. scsi_host_scan_allowed() fails because the adapter state is set to SHOST_RECOVERY instead of SHOST_RUNNING. The state of the adapter is being set to SHOST_RECOVERY by scsi_eh_scmd_add() during error handling. This problem is avoided by moving the setting of the allow_restart flag to later in the device initialization sequence. This prevents further error handling if we get a NOT_READY response from a TUR command by causing scsi_check_sense() to return SUCCESS. Therefore, scsi_eh_scmd_add() will not run and the adapter state will remain as SHOST_RUNNING. Signed-off-by: Wayne Boyer <wayneb@linux.vnet.ibm.com> Acked-by: Brian King <brking@linux.vnet.ibm.com> Signed-off-by: James Bottomley <James.Bottomley@suse.de>
Diffstat (limited to 'drivers/scsi/fcoe')
0 files changed, 0 insertions, 0 deletions