From: Jeff Garzik <jgarzik@pobox.com>
To: dougg@torque.net
Cc: Tejun Heo <htejun@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: fix ATA passthrough handling for ATAPI devices
Date: Sat, 21 Oct 2006 17:40:27 -0400 [thread overview]
Message-ID: <453A93CB.9000008@pobox.com> (raw)
In-Reply-To: <453A8E96.9040702@torque.net>
Douglas Gilbert wrote:
> Jeff Garzik wrote:
>> I'm talking about the changes to the implementation, which appear to
>> mistakenly allow 16-byte CDBs through to the ATAPI device, even if it
>> only supports 12-byte CDBs.
>>
>> I am quite aware of the ATA passthru SCSI command. Heck, the spec had
>> input from me. I'm talking about something different.
> The above were attempts to send IDENTIFY PACKET DEVICE
> to the PATAPI cd/dvd drive via the ATA PASS THROUGH
> (16 and 12) commands respectively. The first one caught
> my attention. Why did it fail with a DID_ABORT?
>
> Whatever the reason both responses are wrong. The second
> one is wrong because
> - the cd/dvd drive does support that opcode (the error
> should be either not ready or incompatible format), or
> - it didn't do the ATA PASS THROUGH (12) properly
The thread has moved on from discussing the acknowledged problem to
discussing the solution.
To summarize my quoted email above, I'm talking about problems with the
implementation details. There are two engineering constraints which a
solution must not violate:
1) The kernel must prevent 16-byte non-passthru commands from reaching
12-byte-only ATAPI devices.
2) Existing in-the-field solutions that issue commands such as BLANK or
a vendor-reserved 0x85 opcode must continue working, without recompile.
Jeff
next prev parent reply other threads:[~2006-10-21 21:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 5:09 [PATCH] libata: fix ATA passthrough handling for ATAPI devices Tejun Heo
2006-10-21 19:16 ` Jeff Garzik
2006-10-21 20:00 ` Douglas Gilbert
2006-10-21 20:13 ` Jeff Garzik
2006-10-21 21:18 ` Douglas Gilbert
2006-10-21 21:40 ` Jeff Garzik [this message]
2006-10-21 23:11 ` Douglas Gilbert
2006-10-23 2:55 ` Tejun Heo
2006-10-23 13:58 ` Douglas Gilbert
2006-11-01 2:03 ` Jeff Garzik
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=453A93CB.9000008@pobox.com \
--to=jgarzik@pobox.com \
--cc=dougg@torque.net \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
/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).