mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Re: Re: Re: BUG in kernel: Wrong Handling of USB HDD’s in scsiglue(slave_configure) and scsi/sd(sd_read_cache_type)
       [not found] <CADDb1s2bVY04G1fZ=3KwCagZHm_dOmLPxsUBKven7=iBo_nU-g@mail.gmail.com>
@ 2011-10-03 14:25 ` Alan Stern
  2011-10-03 16:06   ` Douglas Gilbert
  0 siblings, 1 reply; 7+ messages in thread
From: Alan Stern @ 2011-10-03 14:25 UTC (permalink / raw)
  To: Amit Sahrawat
  Cc: James Bottomley, linux-usb, linux-scsi, linux-kernel,
	linux-fsdevel, Christoph Hellwig

On Mon, 3 Oct 2011, Amit Sahrawat wrote:

> Hi,
> 
> Please find the USB Analyzer - logs for '6' USB based Mass Storage
> devices attached.

Too bad the analyzer log presents only the response, not the command.

> So, only for one of the USB HDD(Seagate - Free Agent), the response
> obtained is correct.

I don't understand the format of the Seagate Free Agent MODE SENSE
data.  Maybe someone else can interpret it; here it is for reference:

SCSI Op(3) ADDR(4) Tag(0x00000004) SCSI CDB MODE SENSE(6)
_______| Data(
__ 000: 1C 00 00 00 86 0B 00 02 00 00 12 A1 9E B0 3C 01 00 1A 0A 00 01 00 00 00 00 00 00 0B B8 00 00 00 
__ 032: 00 00 00 00 1A 0A 00 01 00 00 00 00 00 00 0B B8 A2 06 00 00 00 00 00 00 78 20 55 53 42 32 2E 30 
__ 064: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 7F FF 00 00 00 00 80 FA 0B C2 50 21 4E 41 30 42 
__ 096: 36 58 33 4C 00 30 00 00 00 32 43 46 45 39 42 00 70 F5 12 00 74 FF 00 00 00 00 00 00 00 00 00 00 
__ 128: 3C 00 00 0B B8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 02 50 01 
__ 160: 46 72 65 65 41 67 65 6E 74 20 47 6F 46 6C 65 78 10 50 11 46 72 65 65 41 67 65 6E 74 20 47 6F 46)

For the other devices this seems clear enough.  In most of the cases,
the data doesn't include the Caching page.  The Samsung and Transcend
devices _do_ provide their Caching pages, and in both of them the data
says that write caching is disabled.  (In the Samsung case this is
wrong undoubtedly because of the JMicron bridge -- JMicron's firmware
is notoriously buggy.)

If you can suggest a robust way of determining whether or not a drive 
supports SAT (one which won't cause non-supporting devices to crash), 
it could be added.  In the meantime, I'm not sure what else we can do.

Would it make sense to assume write caching is present and enabled if 
the drive does not provide a Caching page?

Alan Stern


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: BUG in kernel: Wrong Handling of USB HDD’s in scsiglue(slave_configure) and scsi/sd(sd_read_cache_type)
  2011-10-03 14:25 ` Re: Re: BUG in kernel: Wrong Handling of USB HDD’s in scsiglue(slave_configure) and scsi/sd(sd_read_cache_type) Alan Stern
@ 2011-10-03 16:06   ` Douglas Gilbert
  2011-10-03 18:10     ` Alan Stern
  0 siblings, 1 reply; 7+ messages in thread
From: Douglas Gilbert @ 2011-10-03 16:06 UTC (permalink / raw)
  To: Alan Stern
  Cc: Amit Sahrawat, James Bottomley, linux-usb, linux-scsi,
	linux-kernel, linux-fsdevel, Christoph Hellwig

On 11-10-03 04:25 PM, Alan Stern wrote:
> On Mon, 3 Oct 2011, Amit Sahrawat wrote:
>
>> Hi,
>>
>> Please find the USB Analyzer - logs for '6' USB based Mass Storage
>> devices attached.
>
> Too bad the analyzer log presents only the response, not the command.
>
>> So, only for one of the USB HDD(Seagate - Free Agent), the response
>> obtained is correct.
>
> I don't understand the format of the Seagate Free Agent MODE SENSE
> data.  Maybe someone else can interpret it; here it is for reference:
>
> SCSI Op(3) ADDR(4) Tag(0x00000004) SCSI CDB MODE SENSE(6)
> _______| Data(
> __ 000: 1C 00 00 00 86 0B 00 02 00 00 12 A1 9E B0 3C 01 00 1A 0A 00 01 00 00 00 00 00 00 0B B8 00 00 00
> __ 032: 00 00 00 00 1A 0A 00 01 00 00 00 00 00 00 0B B8 A2 06 00 00 00 00 00 00 78 20 55 53 42 32 2E 30
> __ 064: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 7F FF 00 00 00 00 80 FA 0B C2 50 21 4E 41 30 42
> __ 096: 36 58 33 4C 00 30 00 00 00 32 43 46 45 39 42 00 70 F5 12 00 74 FF 00 00 00 00 00 00 00 00 00 00
> __ 128: 3C 00 00 0B B8 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 02 50 01
> __ 160: 46 72 65 65 41 67 65 6E 74 20 47 6F 46 6C 65 78 10 50 11 46 72 65 65 41 67 65 6E 74 20 47 6F 46)

The RBC device parameters mode page followed by a Power
Condition mode page. The RBC device parameters mode page
is the only SCSI page I have seen (mode, log, VPD, etc)
with a 5 byte field!

Decoded response to a probable MODE SENSE(6) "fetch all
pages" command:
   RBC device parameters mpage:
     WCD=0 [double negative: write cache enabled]
     Logical block size: 512 bytes
     Number of logical blocks: 0x12A19EB0 *** [160 GB]
     Power/performance: 0x3c
     READD: 0 [READ enabled]
     WRITED: 0 [WRITE enabled]
     FORMATD: 0 [FORMAT UNIT enabled]
     LOCKD: 1 [media cannot be locked]
   Power Condition mpage:
     IDLE=0
     STANDBY=1
     IDLE_CONDITION_TIMER=0
     STANDBY_CONDITION_TIMER=0xbb8 [300 seconds]

References: rbc-r10a.pdf [1999] + spc3r26 [2005]

Hopefully Seagate will switch to UAS(P) in the near future.


*** That is _not_ the address of the last valid LB as in
     the SCSI READ CAPACITY command!

> For the other devices this seems clear enough.  In most of the cases,
> the data doesn't include the Caching page.  The Samsung and Transcend
> devices _do_ provide their Caching pages, and in both of them the data
> says that write caching is disabled.  (In the Samsung case this is
> wrong undoubtedly because of the JMicron bridge -- JMicron's firmware
> is notoriously buggy.)
>
> If you can suggest a robust way of determining whether or not a drive
> supports SAT (one which won't cause non-supporting devices to crash),
> it could be added.  In the meantime, I'm not sure what else we can do.
>
> Would it make sense to assume write caching is present and enabled if
> the drive does not provide a Caching page?

No. You need to also take into account the RBC
device parameters mode page if present. See above.

Doug Gilbert

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Re: BUG in kernel: Wrong Handling of USB HDD’s in scsiglue(slave_configure) and scsi/sd(sd_read_cache_type)
  2011-10-03 16:06   ` Douglas Gilbert
@ 2011-10-03 18:10     ` Alan Stern
  2011-10-03 19:32       ` James Bottomley
  0 siblings, 1 reply; 7+ messages in thread
From: Alan Stern @ 2011-10-03 18:10 UTC (permalink / raw)
  To: Douglas Gilbert
  Cc: Amit Sahrawat, James Bottomley, linux-usb, linux-scsi,
	linux-kernel, linux-fsdevel, Christoph Hellwig

On Mon, 3 Oct 2011, Douglas Gilbert wrote:

> The RBC device parameters mode page followed by a Power
> Condition mode page. The RBC device parameters mode page
> is the only SCSI page I have seen (mode, log, VPD, etc)
> with a 5 byte field!
> 
> Decoded response to a probable MODE SENSE(6) "fetch all
> pages" command:
>    RBC device parameters mpage:
>      WCD=0 [double negative: write cache enabled]
>      Logical block size: 512 bytes
>      Number of logical blocks: 0x12A19EB0 *** [160 GB]
>      Power/performance: 0x3c
>      READD: 0 [READ enabled]
>      WRITED: 0 [WRITE enabled]
>      FORMATD: 0 [FORMAT UNIT enabled]
>      LOCKD: 1 [media cannot be locked]
>    Power Condition mpage:
>      IDLE=0
>      STANDBY=1
>      IDLE_CONDITION_TIMER=0
>      STANDBY_CONDITION_TIMER=0xbb8 [300 seconds]
> 
> References: rbc-r10a.pdf [1999] + spc3r26 [2005]
> 
> Hopefully Seagate will switch to UAS(P) in the near future.
> 
> 
> *** That is _not_ the address of the last valid LB as in
>      the SCSI READ CAPACITY command!

Thanks for the explanation.

> > Would it make sense to assume write caching is present and enabled if
> > the drive does not provide a Caching page?
> 
> No. You need to also take into account the RBC
> device parameters mode page if present. See above.

All right, suppose neither page is present.  Does it then make sense to 
assume by default that write caching is enabled?

Alan Stern


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Re: BUG in kernel: Wrong Handling of USB HDD’s in scsiglue(slave_configure) and scsi/sd(sd_read_cache_type)
  2011-10-03 18:10     ` Alan Stern
@ 2011-10-03 19:32       ` James Bottomley
  2011-10-03 19:53         ` Alan Stern
  0 siblings, 1 reply; 7+ messages in thread
From: James Bottomley @ 2011-10-03 19:32 UTC (permalink / raw)
  To: Alan Stern
  Cc: Douglas Gilbert, Amit Sahrawat, linux-usb, linux-scsi,
	linux-kernel, linux-fsdevel, Christoph Hellwig

On Mon, 2011-10-03 at 14:10 -0400, Alan Stern wrote:
> > No. You need to also take into account the RBC
> > device parameters mode page if present. See above.
> 
> All right, suppose neither page is present.  Does it then make sense to 
> assume by default that write caching is enabled?

You're the USB expert ... if we do that, we'll start sending
SYNCHRONIZE_CACHE commands down to a whole slew of devices we didn't
before ... is that going to cause problems with any USB SATLs?

James



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Re: BUG in kernel: Wrong Handling of USB HDD’s in scsiglue(slave_configure) and scsi/sd(sd_read_cache_type)
  2011-10-03 19:32       ` James Bottomley
@ 2011-10-03 19:53         ` Alan Stern
  0 siblings, 0 replies; 7+ messages in thread
From: Alan Stern @ 2011-10-03 19:53 UTC (permalink / raw)
  To: James Bottomley
  Cc: Douglas Gilbert, Amit Sahrawat, linux-usb, linux-scsi,
	linux-kernel, linux-fsdevel, Christoph Hellwig

On Mon, 3 Oct 2011, James Bottomley wrote:

> On Mon, 2011-10-03 at 14:10 -0400, Alan Stern wrote:
> > > No. You need to also take into account the RBC
> > > device parameters mode page if present. See above.
> > 
> > All right, suppose neither page is present.  Does it then make sense to 
> > assume by default that write caching is enabled?
> 
> You're the USB expert ... if we do that, we'll start sending
> SYNCHRONIZE_CACHE commands down to a whole slew of devices we didn't
> before ... is that going to cause problems with any USB SATLs?

Hmmm...  Actually, I doubt it would bother any SATLs, but it might well
bother other sorts of USB translation layers.  No way to tell without
trying it, and I don't really want to deal with the fallout.

Maybe a better question to be asking is this: What happens when one of 
these drives (the ones that report their caching capabilities 
incorrectly) is plugged into a Windows system?

Alan Stern


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Re: BUG in kernel: Wrong Handling of USB HDD’s in scsiglue(slave_configure) and scsi/sd(sd_read_cache_type)
  2011-09-30 18:17 ` Alan Stern
@ 2011-09-30 18:36   ` Amit Sahrawat
  0 siblings, 0 replies; 7+ messages in thread
From: Amit Sahrawat @ 2011-09-30 18:36 UTC (permalink / raw)
  To: Alan Stern
  Cc: James Bottomley, linux-usb, linux-scsi, linux-kernel,
	linux-fsdevel, Christoph Hellwig

On Fri, Sep 30, 2011 at 11:47 PM, Alan Stern <stern@rowland.harvard.edu> wrote:
> On Fri, 30 Sep 2011, Amit Sahrawat wrote:
>
>> Adding linux-usb - to get more insight's into the problem.
>>
>> On Fri, Sep 30, 2011 at 11:23 PM, Amit Sahrawat
>> <amit.sahrawat83@gmail.com> wrote:
>> > On Fri, Sep 30, 2011 at 5:48 PM, James Bottomley
>> > <James.Bottomley@hansenpartnership.com> wrote:
>> >> On Fri, 2011-09-30 at 12:26 +0530, Amit Sahrawat wrote:
>> >>> Now, for the USB HDD which do have write cache - sginfo is showing
>> >>> them to Write Cache Enabled as false.
>> >>> Why do the result of hdparm identification and sginfo varies- (I know
>> >>> they have different interface to work with and hdparm takes care of
>> >>> that by using SG_IO interface from it's code)? hdparm showed me
>> >>> correct results - that lead me to digging in the kernel code and
>> >>> checking the performance for USB HDD with Write cache enabled/disabled
>> >>> - which also showed that QUEUE ordering chosen for USB HDD is not
>> >>> correct.
>> >>
>> >> Well, what all this means is the SATL in the USB device is implemented
>> >> wrongly.  Since USB devices only preset SCSI interfaces, that's what we
>> >> have to believe.
>> >>
>> >> hdparm when used correctly sends an ATA inquiry command wrapped in an
>> >> ATA_12 or ATA_16 SCSI command.  A large number of legacy SATLs are known
>> >> to crash on these commands.
>> >>
>> >> Are you sure the ATA command is reporting correctly?  A write back cache
>> >> is a remarkably silly thing to enable for a USB device because they're
>> >> highly likely to be surprise ejected which powers the device down.
>
> A usbmon trace would be very helpful for understanding this.
> Instructions can be found in the kernel source file
> Documentation/usb/usbmon.txt.  Post a trace showing what happens when
> the drive is first plugged in.
Thanks Alan, I will go through the usbmon and check all the
information I can retrieve using that.
>
>> > In addition to the problem reported - there is one more thing I have
>> > noticed with USB HDD - they should be shown as 'removable' but the
>> > removable is marked only for USB PEN Drives. This seems to be a bit of
>> > confusing, any mass storage media connected on USB port should be
>> > recognized as removable.
>
> That is not true.  The word "removable" refers to the storage media.
> Thus, a cdrom drive is removable because you can remove the disc from
> the drive.  The same for a card reader, because you can remove the card
> from the reader.  But a flash drive is not removable, because you can't
> take the flash memory chip out of the device.
>
> You are confusing "removable" with "hot-unpluggable".  All USB drives
> are hot-unpluggable, but relatively few of them are removable.  Vendors
> often get this wrong, however.
I got your point.
>
>> > So, for handling the issue, I would consider adding the handling in
>> > slave_configure()(usb/storage/scsiglue) which marks the HDD/pen drives
>> > as removable also signifying them to be USB based.
>
> This does not happen in usb-storage at all.  The SCSI core is
> responsible for determining whether or not a device is removable, and
> it does this by looking at second byte of the data returned by the SCSI
> INQUIRY command.
>
>> > Then, as part of sd_revalidation – how about adding the ATA_IDENTIFY
>> > command part if the device is USB HDD? As far as the result of
>> > ATA_IDENTIFY is concerned – they return proper ‘256’ bytes - response
>> > and the Words – 82, 85 used for feature supported and enabled/disabled
>> > returns proper values for the USB HDD’s I have seen. In case of USB
>> > pen drives – they return failure – I did not see any crash – maybe I
>> > don’t have one of the legacy SATL based disk.
>> > Since, I am new to this – I will check more on this to get a viable
>> > solution. Please add your opinion. Can you share the name of the
>> > device which causes crash with these ATA commands, If I am able to get
>> > one I can try on that also.
>> >
>> >>> I have a large number of USB HDD's - with different vendors, and for
>> >>> all of them - it is showing Write Cache Enabled as false.
>
> This indicates those drives do not implement the SCSI MODE SENSE
> command correctly.  usbmon will help track down the problem.
Yes, this seems to be the problem. But, almost all the manufacturer's
HDD is behaving the same way. They are showing the effectof switching
Write Cache on/off but not able to detect the same at plug-on.
Anyway, I will look at the 'usbmon' option you have provided.
>
>> >>> The code works only for the Pen Drives or the USB HDD which do not
>> >>> have internal cache.
>> >>>
>> >>> Also, for journalling filesystem being used on USB HDD - it does
>> >>> becomes a cause of concern.
>> >>>
>> >>> Please share your opinion, I guess we need a change for mode sensing
>> >>> in the kernel code for USB HDD.
>> >>
>> >> Well that's a nastily complex problem.  It really needs to be
>> >> whitelisted in the USB stack, but if every drive is doing it, that's
>> >> quite a task.
>> >>
>> >> The question becomes how do we detect in a SCSI fashion that the device
>> >> has a write back cache if none of the standard SCSI mechanisms reports
>> >> it?
>> > As far as detecting in SCSI fashion – I wonder using that I would have
>> > never reached the conclusion that it is the Write Cache of USB HDD
>> > which is causing problem instead I would have been focusing on
>> > particular file system (XFS in my case –which in itself is complex) –
>> > there BARRIER support and also the Queue handling in the elevator with
>> > I/O scheduler.
>> > None of the sg utils is showing anything related with the Write Cache
>> > in USB HDD – which provide any hint that the Cache is enabled – this
>> > is a bit surprising because most of the high end USB mass storages
>> > device in the market have Write Cache in them.
>
> Alan Stern
>
>

Regards,
Amit Sahrawat

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Re: BUG in kernel: Wrong Handling of USB HDD’s in scsiglue(slave_configure) and scsi/sd(sd_read_cache_type)
  2011-09-30 17:56 Amit Sahrawat
@ 2011-09-30 18:17 ` Alan Stern
  2011-09-30 18:36   ` Amit Sahrawat
  0 siblings, 1 reply; 7+ messages in thread
From: Alan Stern @ 2011-09-30 18:17 UTC (permalink / raw)
  To: Amit Sahrawat
  Cc: James Bottomley, linux-usb, linux-scsi, linux-kernel,
	linux-fsdevel, Christoph Hellwig

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=UTF-8, Size: 5333 bytes --]

On Fri, 30 Sep 2011, Amit Sahrawat wrote:

> Adding linux-usb - to get more insight's into the problem.
> 
> On Fri, Sep 30, 2011 at 11:23 PM, Amit Sahrawat
> <amit.sahrawat83@gmail.com> wrote:
> > On Fri, Sep 30, 2011 at 5:48 PM, James Bottomley
> > <James.Bottomley@hansenpartnership.com> wrote:
> >> On Fri, 2011-09-30 at 12:26 +0530, Amit Sahrawat wrote:
> >>> Now, for the USB HDD which do have write cache - sginfo is showing
> >>> them to Write Cache Enabled as false.
> >>> Why do the result of hdparm identification and sginfo varies- (I know
> >>> they have different interface to work with and hdparm takes care of
> >>> that by using SG_IO interface from it's code)? hdparm showed me
> >>> correct results - that lead me to digging in the kernel code and
> >>> checking the performance for USB HDD with Write cache enabled/disabled
> >>> - which also showed that QUEUE ordering chosen for USB HDD is not
> >>> correct.
> >>
> >> Well, what all this means is the SATL in the USB device is implemented
> >> wrongly.  Since USB devices only preset SCSI interfaces, that's what we
> >> have to believe.
> >>
> >> hdparm when used correctly sends an ATA inquiry command wrapped in an
> >> ATA_12 or ATA_16 SCSI command.  A large number of legacy SATLs are known
> >> to crash on these commands.
> >>
> >> Are you sure the ATA command is reporting correctly?  A write back cache
> >> is a remarkably silly thing to enable for a USB device because they're
> >> highly likely to be surprise ejected which powers the device down.

A usbmon trace would be very helpful for understanding this.  
Instructions can be found in the kernel source file 
Documentation/usb/usbmon.txt.  Post a trace showing what happens when 
the drive is first plugged in.

> > In addition to the problem reported - there is one more thing I have
> > noticed with USB HDD - they should be shown as 'removable' but the
> > removable is marked only for USB PEN Drives. This seems to be a bit of
> > confusing, any mass storage media connected on USB port should be
> > recognized as removable.

That is not true.  The word "removable" refers to the storage media.  
Thus, a cdrom drive is removable because you can remove the disc from
the drive.  The same for a card reader, because you can remove the card
from the reader.  But a flash drive is not removable, because you can't
take the flash memory chip out of the device.

You are confusing "removable" with "hot-unpluggable".  All USB drives
are hot-unpluggable, but relatively few of them are removable.  Vendors 
often get this wrong, however.

> > So, for handling the issue, I would consider adding the handling in
> > slave_configure()(usb/storage/scsiglue) which marks the HDD/pen drives
> > as removable also signifying them to be USB based.

This does not happen in usb-storage at all.  The SCSI core is
responsible for determining whether or not a device is removable, and
it does this by looking at second byte of the data returned by the SCSI
INQUIRY command.

> > Then, as part of sd_revalidation – how about adding the ATA_IDENTIFY
> > command part if the device is USB HDD? As far as the result of
> > ATA_IDENTIFY is concerned – they return proper ‘256’ bytes - response
> > and the Words – 82, 85 used for feature supported and enabled/disabled
> > returns proper values for the USB HDD’s I have seen. In case of USB
> > pen drives – they return failure – I did not see any crash – maybe I
> > don’t have one of the legacy SATL based disk.
> > Since, I am new to this – I will check more on this to get a viable
> > solution. Please add your opinion. Can you share the name of the
> > device which causes crash with these ATA commands, If I am able to get
> > one I can try on that also.
> >
> >>> I have a large number of USB HDD's - with different vendors, and for
> >>> all of them - it is showing Write Cache Enabled as false.

This indicates those drives do not implement the SCSI MODE SENSE 
command correctly.  usbmon will help track down the problem.

> >>> The code works only for the Pen Drives or the USB HDD which do not
> >>> have internal cache.
> >>>
> >>> Also, for journalling filesystem being used on USB HDD - it does
> >>> becomes a cause of concern.
> >>>
> >>> Please share your opinion, I guess we need a change for mode sensing
> >>> in the kernel code for USB HDD.
> >>
> >> Well that's a nastily complex problem.  It really needs to be
> >> whitelisted in the USB stack, but if every drive is doing it, that's
> >> quite a task.
> >>
> >> The question becomes how do we detect in a SCSI fashion that the device
> >> has a write back cache if none of the standard SCSI mechanisms reports
> >> it?
> > As far as detecting in SCSI fashion – I wonder using that I would have
> > never reached the conclusion that it is the Write Cache of USB HDD
> > which is causing problem instead I would have been focusing on
> > particular file system (XFS in my case –which in itself is complex) –
> > there BARRIER support and also the Queue handling in the elevator with
> > I/O scheduler.
> > None of the sg utils is showing anything related with the Write Cache
> > in USB HDD – which provide any hint that the Cache is enabled – this
> > is a bit surprising because most of the high end USB mass storages
> > device in the market have Write Cache in them.

Alan Stern


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2011-10-03 19:54 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <CADDb1s2bVY04G1fZ=3KwCagZHm_dOmLPxsUBKven7=iBo_nU-g@mail.gmail.com>
2011-10-03 14:25 ` Re: Re: BUG in kernel: Wrong Handling of USB HDD’s in scsiglue(slave_configure) and scsi/sd(sd_read_cache_type) Alan Stern
2011-10-03 16:06   ` Douglas Gilbert
2011-10-03 18:10     ` Alan Stern
2011-10-03 19:32       ` James Bottomley
2011-10-03 19:53         ` Alan Stern
2011-09-30 17:56 Amit Sahrawat
2011-09-30 18:17 ` Alan Stern
2011-09-30 18:36   ` Amit Sahrawat

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®