linux-kernel - Re: Re: Re: Re: BUG in kernel: Wrong Handling of USB HDD’s in scsiglue(slave_configure) and scsi/sd(sd_read_cache

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1317827831.7238.2.camel@dabdike>
Date:	Wed, 05 Oct 2011 08:17:11 -0700
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Amit Sahrawat <amit.sahrawat83@...il.com>,
	Douglas Gilbert <dgilbert@...erlog.com>,
	linux-usb@...r.kernel.org, linux-scsi@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	Christoph Hellwig <hch@...radead.org>
Subject: Re: Re: Re: Re: BUG in kernel: Wrong Handling of USB
 HDD’s in scsiglue(slave_configure) and
 scsi/sd(sd_read_cache_ =?windows-1252?Q?type=29

On Wed, 2011-10-05 at 10:17 -0400, Alan Stern wrote:
> On Wed, 5 Oct 2011, Amit Sahrawat wrote:
> 
> > Hi,
> > 
> > In order to verify the SYNC_CACHE command being passed.
> > First I checked on the USB HDD(Seagate - Free Agent) which is gettind
> > properly identified on linux. I performed - copy of a file and then
> > did 'Safely Remove Hardware" - this resulted in SYNC_CACHE command
> > being passed - All logs are captured for this.
> > 
> > Then, for the same Hard Disk - I checked for the behaviour on Windows.
> > There is no SYNC CACHE command being passed in this case.
> > 
> > Again, checked for a different hard disk(Seagate) - which has cache
> > but not shown in Linux. In that case also, there is no SYNC CACHE
> > command.
> > 
> > Please find the logs for the '3' cases attached.
> 
> This is a little disappointing.  If Windows doesn't use the SYNCHRONIZE 
> CACHE command, it's quite likely that some USB drives will crash when 
> they receive it.
> 
> This strongly suggests that we should not change the current code.

I agree ... it means they go by the SCSI mode pages too, so we'll be no
worse than they are.  Plus we don't risk upsetting the rest of the USB
device universe.

James


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/