From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Greg KH <greg@kroah.com>
Cc: USB development list <linux-usb-devel@lists.sourceforge.net>,
linux-scsi@vger.kernel.org,
USB Storage list <usb-storage@lists.one-eyed-alien.net>,
linux-usb@vger.kernel.org, David Brown <usb-storage2@davidb.org>,
Stefan Richter <stefanr@s5r6.in-berlin.de>,
Alan Stern <stern@rowland.harvard.edu>,
Hans de Goede <j.w.r.degoede@hhs.nl>,
Boaz Harrosh <bharrosh@panasas.com>,
Matthew Dharm <mdharm-scsi@one-eyed-alien.net>
Subject: Re: PATCH: usb-storage-set-last-sector-bug-flag.patch
Date: Fri, 25 Jan 2008 11:12:21 -0600 [thread overview]
Message-ID: <1201281141.3119.41.camel@localhost.localdomain> (raw)
In-Reply-To: <20080124172158.GC9665@kroah.com>
On Thu, 2008-01-24 at 09:21 -0800, Greg KH wrote:
> On Thu, Jan 24, 2008 at 06:07:00PM +0100, Stefan Richter wrote:
> > Greg KH wrote:
> > > I just am worried that we are
> > > now suddenly keeping access from the last sector for devices that
> > > currently did work just fine.
> >
> > This new workaround doesn't prevent access to the last sector. It only
> > breaks up a multi-sector access which would also reach the last sector
> > into several (two? I'm too lazy to look back in the mail thread)
> > accesses, in order to access the last sector in a dedicated
> > single-sector access.
> >
> > So that's very differently to the fix-capacity workaround. The
> > fix-capacity workaround manipulates the READ CAPACITY parameter data.
> > Therefore the fix-capacity workaround is unsafe for non-buggy devices.
> >
> > The last-sector-(access-)bug workaround _only_ modifies the command
> > stream which is sent to the device. A dangerous command is replaced by
> > equivalent safe commands. These commands are luckily safe for _all_
> > devices, buggy and non-buggy ones. The only cost of this workaround is
> > (1.) the code, (2.) the runtime/ bandwidth/ latency overhead for
> > accesses which reach the last sector.
>
> Ok, thanks for explaining it better. I have no objection to this change
> anymore.
So, for forms sake to take this through the SCSI tree I need at least
one USB person to ack it ...
James
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
next prev parent reply other threads:[~2008-01-25 17:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-20 10:27 PATCH: usb-storage-set-last-sector-bug-flag.patch Hans de Goede
2008-01-20 20:56 ` Greg KH
[not found] ` <20080120205625.GB28842-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2008-01-20 21:03 ` James Bottomley
[not found] ` <1200863008.3105.30.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-01-20 21:25 ` Hans de Goede
2008-01-20 21:39 ` [usb-storage] " Guillaume Bedot
2008-01-20 21:45 ` Alan Stern
2008-01-23 18:12 ` Greg KH
[not found] ` <20080123181239.GA21836-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2008-01-23 18:39 ` James Bottomley
2008-01-23 18:50 ` Greg KH
2008-01-24 17:07 ` Stefan Richter
2008-01-24 17:21 ` Greg KH
2008-01-25 17:12 ` James Bottomley [this message]
2008-01-25 19:23 ` Matthew Dharm
[not found] ` <4798C5B4.1000208-MtYdepGKPcBMYopoZt5u/LNAH6kLmebB@public.gmane.org>
2008-01-24 17:22 ` Stefan Richter
[not found] ` <47932211.90105-fbo2DhPpy/Q@public.gmane.org>
2008-01-22 8:26 ` [usb-storage] " Guillaume Bedot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1201281141.3119.41.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=bharrosh@panasas.com \
--cc=greg@kroah.com \
--cc=j.w.r.degoede@hhs.nl \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux-usb@vger.kernel.org \
--cc=mdharm-scsi@one-eyed-alien.net \
--cc=stefanr@s5r6.in-berlin.de \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage2@davidb.org \
--cc=usb-storage@lists.one-eyed-alien.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).