From: Andries Brouwer <Andries.Brouwer@cwi.nl>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andries Brouwer <Andries.Brouwer@cwi.nl>,
Luben Tuikov <luben_tuikov@adaptec.com>,
SCSI development list <linux-scsi@vger.kernel.org>,
USB Storage list <usb-storage@lists.one-eyed-alien.net>
Subject: Re: [usb-storage] Re: Handling erroneous READ CAPACITY response in sd.c
Date: Fri, 5 Nov 2004 22:59:37 +0100 [thread overview]
Message-ID: <20041105215935.GD10912@apps.cwi.nl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0411051632440.1015-100000@ida.rowland.org>
On Fri, Nov 05, 2004 at 04:38:07PM -0500, Alan Stern wrote:
> No. I said that it _could_ be moved to a SCSI blist but would probably be
> better off remaining in unusual_devices. What should be changed is the
> way we handle these devices. Right now usb-storage alters the data sent
> by the device, before anyone else can see it. My proposal is that
> usb-storage pass the data unchanged and sd_read_capacity() change the
> value it gets if the device is known to be bad.
OK - yes, I agree.
Andries
next prev parent reply other threads:[~2004-11-05 21:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 19:19 Handling erroneous READ CAPACITY response in sd.c Alan Stern
2004-10-19 20:58 ` Luben Tuikov
2004-10-19 21:52 ` Alan Stern
2004-10-20 12:40 ` Luben Tuikov
2004-10-20 15:48 ` Alan Stern
2004-10-24 12:34 ` Eero Volotinen
2004-10-25 19:41 ` Alan Stern
2004-10-25 20:27 ` Luben Tuikov
2004-10-25 20:08 ` Luben Tuikov
[not found] ` <417D6123.4060902@ping-viini.org>
2004-10-25 20:55 ` Luben Tuikov
2004-11-05 16:18 ` Alan Stern
2004-11-05 18:06 ` Matthew Dharm
2004-11-05 18:34 ` Alan Stern
2004-11-05 18:44 ` [usb-storage] " Andries Brouwer
2004-11-05 21:38 ` Alan Stern
2004-11-05 21:59 ` Andries Brouwer [this message]
2004-11-08 18:55 ` Luben Tuikov
2004-11-08 21:03 ` Alan Stern
2004-11-08 21:35 ` Luben Tuikov
2004-11-08 22:04 ` Matthew Dharm
2004-11-08 22:08 ` Alan Stern
2004-10-20 13:28 ` Luben Tuikov
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=20041105215935.GD10912@apps.cwi.nl \
--to=andries.brouwer@cwi.nl \
--cc=linux-scsi@vger.kernel.org \
--cc=luben_tuikov@adaptec.com \
--cc=stern@rowland.harvard.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.