> > Well, that might be a problem if it weren't for the fact that this > LUN_INHIBIT flag was removed in 2002. If it's taken three > years to find > a device that has a problem with it, I don't really think it's a > particularly widespread problem. > > ...snip.... > > James > Just as an FYI to shed some light.... It took Western Digital 3 years to find the problem because September (back when I started the other conversation about this topic) was the first time we've tried to get access to a USB storage device under Linux using a passthru CDB. Maxtor and Seagate might be in a similar boat (but obviously that's just speculation), and it's not like thumb drives need ATA passthru support. This also isn't the first time a kernel issue has been around for a while, but nobody noticed. Fixed in 2.6.14 was a bug that existed for (as far as I can tell) all of 2.6.x. The kernel would oops on pio-out HDIO_DRIVE_TASKFILE ioctls because of a null pointer. The first time I tried to do a pio-out command I hit it, yet nobody had complained about it as far as I could tell. The kernel 2.6.x series has been out how long? I was baffled and my only guess was that even though the API was there for pio-out, nobody was using it. I wonder if it's the same issue with vendor specific cdbs to USB storage devices; nobody is really using it? The cypress passthru CDB works fine under Windows, and since most companies only care about Windows, they probably didn't even try to get it to work under Linux. For instance I wasn't even told to support it under Linux until some people hit a Windows limitation they couldn't get around. The other possibility is that for groups that do use vendor specific CDBs and have never had this issue, they probably have CDBs that don't stick meaningful bits where the LUN goes, so therefore it was never an issue. However, both the ATACB and the SAT passthru CDB have meaningful bits there. Regards, Tim Thelin - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html