aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorbrking@us.ibm.com <brking@us.ibm.com>2005-11-01 17:00:11 -0600
committerJames Bottomley <jejb@mulgrave.(none)>2005-11-06 12:59:48 -0600
commit11cd8f120173a707e9ed7b78f7af8cde5a1ebb90 (patch)
tree3e2fe64fc9a3cebb932364253d4d7fb71946c25e
parentd6933df97a486d9c73a6bb4fed75154343c8638f (diff)
downloadkernel_samsung_smdk4412-11cd8f120173a707e9ed7b78f7af8cde5a1ebb90.zip
kernel_samsung_smdk4412-11cd8f120173a707e9ed7b78f7af8cde5a1ebb90.tar.gz
kernel_samsung_smdk4412-11cd8f120173a707e9ed7b78f7af8cde5a1ebb90.tar.bz2
[SCSI] ipr: Disk array rescanning fix
IPR RAID arrays show up on a virtual scsi bus, with a scsi bus number of 255, which is generated by the adapter microcode. For the initial scan of the host, we manually scan this bus since it does not obey SAM in regards to sparse LUNs and the disk array devices do not have a consistent product id to use scsi core's blacklist. If /proc/scsi/scsi or sysfs is used to delete one of these devices, the device will not be able to get added back by rescanning the host since scsi core will see ipr's max_channel as 4, rather than 255. Update max_channel after the initial scan so that ipr raid arrays can get re-added if they get deleted. Signed-off-by: Brian King <brking@us.ibm.com> Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
-rw-r--r--drivers/scsi/ipr.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/scsi/ipr.c b/drivers/scsi/ipr.c
index e0039df..da61ce1 100644
--- a/drivers/scsi/ipr.c
+++ b/drivers/scsi/ipr.c
@@ -6008,6 +6008,7 @@ static int __devinit ipr_probe(struct pci_dev *pdev,
ipr_scan_vsets(ioa_cfg);
scsi_add_device(ioa_cfg->host, IPR_IOA_BUS, IPR_IOA_TARGET, IPR_IOA_LUN);
ioa_cfg->allow_ml_add_del = 1;
+ ioa_cfg->host->max_channel = IPR_VSET_BUS;
schedule_work(&ioa_cfg->work_q);
return 0;
}