From: Boaz Harrosh <bharrosh@panasas.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH v2] SCSI: detect missing data for INQUIRY
Date: Wed, 03 Dec 2008 20:46:23 +0200 [thread overview]
Message-ID: <4936D3FF.1040500@panasas.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0812031315490.2518-100000@iolanthe.rowland.org>
Alan Stern wrote:
> On Wed, 3 Dec 2008, James Bottomley wrote:
>
>> On Wed, 2008-12-03 at 12:44 -0500, Alan Stern wrote:
>>> James:
>>>
>>> There hasn't been any feedback on this patch:
>>>
>>> http://marc.info/?l=linux-scsi&m=122513368301598&w=2
>>>
>>> It was modified in the way you requested. Does it need to be revised
>>> any more?
>> Probably not. I really dislike a check and retry on something which is
>> theoretically a legal return, but I suppose I can put it in and see if
>> anything breaks.
>
> It's too bad that the scsi_execute_req() interface loses all
> information about how much data the device actually sent. If that
> information were preserved then it wouldn't be necessary to rely on
> this not-quite-satisfactory sort of test.
>
> Alan Stern
>
Just a comment:
You are the third person this week that wanted residual return from
scsi_execute/scsi_execute_req. Perhaps it's time as come ;)
(This is a TODO for me)
Boaz
next prev parent reply other threads:[~2008-12-03 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 17:44 [PATCH v2] SCSI: detect missing data for INQUIRY Alan Stern
2008-12-03 18:00 ` James Bottomley
2008-12-03 18:18 ` Alan Stern
2008-12-03 18:46 ` Boaz Harrosh [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-27 17:29 [PATCH] " James Bottomley
2008-10-27 18:53 ` [PATCH v2] " Alan Stern
2008-10-28 13:02 ` James Smart
2008-10-28 13:43 ` Alan Stern
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=4936D3FF.1040500@panasas.com \
--to=bharrosh@panasas.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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