Searched hist:"22 ffeb48b7584d6cd50f2a595ed6065d86a87459" (Results 1 – 2 of 2) sorted by relevance
| /linux/include/scsi/ |
| H A D | scsi_devinfo.h | diff 22ffeb48b7584d6cd50f2a595ed6065d86a87459 Tue Jun 03 10:58:53 CEST 2014 Hannes Reinecke <hare@suse.de> scsi_scan: Restrict sequential scan to 256 LUNs
Sequential scan for more than 256 LUNs is very fragile as
LUNs might not be numbered sequentially after that point.
SAM revisions later than SCSI-3 impose a structure on
LUNs larger than 256, making LUN numbers between 256
and 16384 illegal.
SCSI-3, however allows for plain 64-bit numbers with
no internal structure.
So restrict sequential LUN scan to 256 LUNs and add a
new blacklist flag 'BLIST_SCSI3LUN' to scan up to
max_lun devices.
Signed-off-by: Hannes Reinecke <hare@suse.de>
Reviewed-by: Ewan Milne <emilne@redhat.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
|
| /linux/drivers/scsi/ |
| H A D | scsi_scan.c | diff 22ffeb48b7584d6cd50f2a595ed6065d86a87459 Tue Jun 03 10:58:53 CEST 2014 Hannes Reinecke <hare@suse.de> scsi_scan: Restrict sequential scan to 256 LUNs
Sequential scan for more than 256 LUNs is very fragile as
LUNs might not be numbered sequentially after that point.
SAM revisions later than SCSI-3 impose a structure on
LUNs larger than 256, making LUN numbers between 256
and 16384 illegal.
SCSI-3, however allows for plain 64-bit numbers with
no internal structure.
So restrict sequential LUN scan to 256 LUNs and add a
new blacklist flag 'BLIST_SCSI3LUN' to scan up to
max_lun devices.
Signed-off-by: Hannes Reinecke <hare@suse.de>
Reviewed-by: Ewan Milne <emilne@redhat.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
|