Re: [PATCH] 2.4.23

[Christoph Hellwig <hch@infradead.org>]

On Wed, Dec 17, 2003 at 08:13:40AM -0800, Frank Borich wrote:
> Hi All,
> 
> My name is Frank Borich, representing Xyratex International
> (http://www.xyratex.com).  We design, and manufacture Data Storage
> Subsystems.  During integration testing, we discovered that a patch to
> scsi_scan.c is required (2.4.x kernels only), in order to set the
> BLIST_SPARSELUN flag for our subsystems.  This flag adds support for
> non-contiguous lun numbering.  We are unable to use the already
> implemented "device_list" to set flags for our subsystems.  This is due
> to the fact that we sell only to OEMs, and vendor name will change.
> Rather than submit a separate patch for each branded subsystem we can
> look elsewhere in the SCSI inquiry data, and set the flag accordingly.
> The logic below, is executed once the end of the device_list is reached.
> When the end of the table is reached, a memcmp is issued to look for a
> particular string located at offset 96.  If the string is found, the
> flag BLIST_SPARSELUN is returned.  Below is a patch for the SCSI driver
> (scsi_scan.c). 

I'm not too happy about the form of this patch. Could you cook up one
for 2.6.0 that adds a function pointer to poke at the inquiry data
to the blacklist?  We could backport it to 2.4 later.