Re: [PATCH] Ghost devices being reported with AIC7XXX version 6.2.6

[Mike Brown <mbrown@emc.com>]

I'd rather have to add a list entry for one of a few dozen storage
array vendors then get hundreds bug reports from noname USB
block devices that blew up when we sent REPORT_LUNS.  Considering
a lot of them blow up if you ask for more than a 36 byte INQUIRY
response, I think REPORT_LUNS should be special cased in the
blacklist.

I haven't been tracking 2.5, but I knew there were plans to push
push the scanning code and the blacklist stuff into a userspace
scsid.  Did this make it?

On Thu, Oct 31, 2002 at 12:41:50PM -0800, Matthew Jacob wrote:
> 
> Yeah, but lets get out of the tailchasing exercise of list updates if we
> can...
> 
> 
> > > And we recently added INQUIRY with the EVPD bit set and an EVPD page 0.  
> > > >From the reports I've seen, I'm pretty sure it's causing a more than
> > > trivial number of devices to lock up on boot.  I suspect blindly pulling a
> > > REPORT_LUNS on SCSI-2 devices would likely cause similar problems.
> > 
> > What about adding BLIST_FORCE_REPORT_LUNS?
> > 
> > -Michael F. Brown, EMC Corp.
> > 
> > Email:            mbrown@emc.com
> > EMC Tie Line:             x43416
> > External Line:    (508) 249-3416
> > 
> > "5 years from now everyone will be running free
> >  GNU on their 200 MIPS, 64M SPARCstation-5."      -Andrew Tanenbaum '92
> > 
> > (In late 1997 I installed Linux for the first time on my 200Mhz, 128M
> >  AMD x86 clone)
> > 
-Michael F. Brown, EMC Corp.

Email:            mbrown@emc.com
EMC Tie Line:             x43416
External Line:    (508) 249-3416

"5 years from now everyone will be running free
 GNU on their 200 MIPS, 64M SPARCstation-5."      -Andrew Tanenbaum '92

(In late 1997 I installed Linux for the first time on my 200Mhz, 128M
 AMD x86 clone)