blacklist microtek scanmaker III

2005-02-23 Thread Dave Jones
To try and escape the madness of adding a zillion USB card readers
to the SCSI whitelist, I flipped the scan all lun's by default switch
in the fedora kernel recently to see just what breaks, in the hope
of moving from a whitelist solution to a blacklist.

Here's the first (hopefully of not too many) devices that broke.
(See https://bugzilla.redhat.com/beta/show_bug.cgi?id=149402 for more info)

Signed-off-by: Dave Jones [EMAIL PROTECTED]

--- linux-2.6.10/drivers/scsi/scsi_devinfo.c~   2005-02-23 14:27:53.0 
-0500
+++ linux-2.6.10/drivers/scsi/scsi_devinfo.c2005-02-23 14:29:06.0 
-0500
@@ -63,6 +63,7 @@ static struct {
{MAXTOR, XT-4170S, B5A, BLIST_NOLUN}, /* locks up */
{MAXTOR, XT-8760S, B7B, BLIST_NOLUN}, /* locks up */
{MEDIAVIS, RENO CD-ROMX2A, 2.03, BLIST_NOLUN},/* responds to 
all lun */
+   {MICROTEK, ScanMakerIII, 2.30, BLIST_NOLUN},  /* responds to 
all lun */
{NEC, CD-ROM DRIVE:841, 1.0, BLIST_NOLUN},/* locks up */
{PHILIPS, PCA80SC, V4-2, BLIST_NOLUN},/* responds to all lun 
*/
{RODIME, RO3000S, 2.33, BLIST_NOLUN}, /* locks up */
-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: blacklist microtek scanmaker III

2005-02-23 Thread Bryan Henderson
I notice that Scanmaker II is already in the list, apparently in the wrong 
place.  Maybe you could fix that in the same patch, so the entries are 
conveniently together.

Also: the only reason this caught my eye is that just a few days ago, I 
discovered my Scanmaker I has the same problem (responds to all LUNs) and 
investigated briefly.  I guess I should get the vendor/model for it and 
throw that in too.

-
To unsubscribe from this list: send the line unsubscribe linux-scsi in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html