linux-kernel - Re: usb-storage, error reading the last 8 sectors, regression in 2.6.25-rc7

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <Pine.LNX.4.44L0.0804011040260.4253-100000@iolanthe.rowland.org>
Date:	Tue, 1 Apr 2008 10:42:51 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Matthew Dharm <mdharm-kernel@...-eyed-alien.net>
cc:	Oliver Neukum <oliver@...kum.org>,
	Sergey Dolgov <solkaa@...il.com>,
	<linux-kernel@...r.kernel.org>, <linux-usb@...r.kernel.org>
Subject: Re: usb-storage, error reading the last 8 sectors, regression in
 2.6.25-rc7

On Tue, 1 Apr 2008, Matthew Dharm wrote:

> On Tue, Apr 01, 2008 at 10:28:52AM -0400, Alan Stern wrote:
> > On Tue, 1 Apr 2008, Oliver Neukum wrote:
> > 
> > > Am Dienstag, 1. April 2008 03:58:31 schrieb Alan Stern:
> > > > Nevertheless, it's clear that the problem has nothing to do with the 
> > > > USB stack.  The real source of the problem lies in the device itself, 
> > > > for reporting a bogus error when in fact nothing went wrong.  That may 
> > > > also explain why you don't always see the problem -- sometimes the 
> > > > device works the way it ought to.
> > > 
> > > Reminds me of the devices that can read the last sector but only if it is read
> > > by itself. Do you reckon this device may have the "opposite" quirk?
> > 
> > Could be something like that.
> 
> Didn't I see some SCSI patches go by to implement exactly this change?
> That is, only read the last sector by itself?

You are getting the two problems mixed up.  The older problem, which
the SCSI patche addressed, was that the device would fail when
accessing the last sector unless the transfer was 1 sector long.

This problem is different.  When performing an 8-sector read that 
includes the last sector, the device succeeds.  When performing a 
7-sector read starting from the same place (so not including the last 
sector), the device fails.

Alan Stern

--
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/