From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Tejun Heo <htejun@gmail.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Douglas Gilbert <dougg@torque.net>
Subject: Re: [PATCH 2.6.20-rc3] fix broken retval test in sr_block_ioctl
Date: Tue, 02 Jan 2007 17:52:43 -0500 [thread overview]
Message-ID: <459AE23B.1020904@rtr.ca> (raw)
In-Reply-To: <459ADEB1.7080505@pobox.com>
Jeff Garzik wrote:
> Mark Lord wrote:
..
>> Allow ATA_12 / ATA_16 passthru commands to be issued for ATAPI devices
>
> Douglas Gilbert noticed this a while ago.
>
> The patch's technical content is fine, but there is an open policy
> question: For some devices, there is an opcode overlap (BLANK? Doug
> probably remembers the issue better than I). And from a practical
> standpoint, to handle any vendor weird-isms (nahhh those never happen in
> ATAPI), it would be nice to be able to force the current (pre-mlord
> patch) behavior to ensure that all opcodes are passed to ATAPI.
>
> Absent a better idea, I would simply suggest adding a module parameter
> that restores the "all opcodes are passed to device, guaranteed" mode.
>
> I'm fine with changing the default behavior to that which is presented
> by your patch.
Mmmm.. yes, the "BLANK" opcode is indeed the same as ATA_12.
That looks rather dangerous to me -- isn't BLANK commonly used
with CD-RW discs and the like? (gotta test that now..)
If so, then perhaps all we can support is ATA_16, except the upper
layers mightn't even pass them to libata without a bit of hackery.
I'll go and see about BLANK now..
Cheers
Mark
next prev parent reply other threads:[~2007-01-02 22:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 22:24 [PATCH 2.6.20-rc3] fix broken retval test in sr_block_ioctl Mark Lord
2007-01-02 22:30 ` Mark Lord
2007-01-02 22:32 ` [PATCH] Add ATA_12/ATA_16 support for libata ATAPI Mark Lord
2007-01-02 22:36 ` [PATCH] libata use ATA_12 in HDIO_* ioctls for ATAPI compatibility Mark Lord
2007-01-03 0:23 ` Mark Lord
2007-01-02 22:37 ` [PATCH 2.6.20-rc3] fix broken retval test in sr_block_ioctl Jeff Garzik
2007-01-02 22:52 ` Mark Lord [this message]
2007-01-02 23:12 ` Mark Lord
2007-01-03 3:36 ` Douglas Gilbert
2007-01-02 22:32 ` Jeff Garzik
2007-01-02 22:39 ` Mark Lord
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=459AE23B.1020904@rtr.ca \
--to=liml@rtr.ca \
--cc=akpm@osdl.org \
--cc=dougg@torque.net \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.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).