diff options
author | dave wysochanski <davidw@netapp.com> | 2006-08-09 14:56:32 -0400 |
---|---|---|
committer | James Bottomley <jejb@mulgrave.il.steeleye.com> | 2006-08-19 13:37:40 -0700 |
commit | 84961f28e9d13a4b193d0c8545f3c060c1890ff3 (patch) | |
tree | 11ad36484d5a891a2455d876dfd9cf6fd82f51f3 /drivers/scsi/aic7xxx_old.c | |
parent | 8c867b257d159ca04602d7087fa29f846785f9ea (diff) | |
download | kernel_samsung_smdk4412-84961f28e9d13a4b193d0c8545f3c060c1890ff3.zip kernel_samsung_smdk4412-84961f28e9d13a4b193d0c8545f3c060c1890ff3.tar.gz kernel_samsung_smdk4412-84961f28e9d13a4b193d0c8545f3c060c1890ff3.tar.bz2 |
[SCSI] Don't add scsi_device for devices that return PQ=1, PDT=0x1f
Some targets may return slight variations of PQ and PDT to indicate
no LUN mapped. USB UFI setting PDT=0x1f but having reserved bits for
PQ is one example, and NetApp targets returning PQ=1 and PDT=0x1f is
another. Both instances seem like reasonable responses according to
SPC-3 and UFI specs.
The current scsi_probe_and_add_lun() code adds a scsi_device
for targets that return PQ=1 and PDT=0x1f. This causes LUNs of type
"UNKNOWN" to show up in /proc/scsi/scsi when no LUNs are mapped.
In addition, subsequent rescans fail to recognize LUNs that may be
added on the target, unless preceded by a write to the delete attribute
of the "UNKNOWN" LUN.
This patch addresses this problem by skipping over the scsi_add_lun()
when PQ=1,PDT=0x1f is encountered, and just returns
SCSI_SCAN_TARGET_PRESENT.
Signed-off-by: Dave Wysochanski <davidw@netapp.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: James Bottomley <James.Bottomley@SteelEye.com>
Diffstat (limited to 'drivers/scsi/aic7xxx_old.c')
0 files changed, 0 insertions, 0 deletions