From: Chuck Ebbert <cebbert@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: LIBATA SCSI command validation changed in 2.6.24
Date: Fri, 11 Jan 2008 16:53:56 -0500 [thread overview]
Message-ID: <4787E574.6020304@redhat.com> (raw)
In-Reply-To: <4787E114.2030301@garzik.org>
On 01/11/2008 04:35 PM, Jeff Garzik wrote:
> Chuck Ebbert wrote:
>> commit 607126c2a21cd6e9bb807fdd415c1a992f7b9009 changed command
>> validation
>> to allow short commands in 16-byte CDBs, but it also made checking more
>> strict. Before the change, a 10-byte SG_IO command could have its
>> length set
>> to 9 and still work. Now it fails. Not sure if this is a bug, but it has
>> caused at least one application to fail that used to work (qpxtool.)
>>
>> [https://bugzilla.redhat.com/show_bug.cgi?id=428281]
>
> Can you get us an example CDB? Its unclear if the hexdump in the bug
> report is a returned mode page or the CDB or what...?
>
Not easily, but the maintainer of that program forced the length of
the MODE_SENSE(10) command to 10 and that command started working.
By looking at the source I could tell that it was setting the command
length to (1 + the index of the last byte written to the CDB) and
only wrote up to offset 8 when building the command, so it must have
been sending the command with a length of 9. (It zeroed the whole CDB
first and only wrote what it needed to.)
(And it used the C++ operator [] to build the command, that was fun
to trace...)
next prev parent reply other threads:[~2008-01-11 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 21:30 LIBATA SCSI command validation changed in 2.6.24 Chuck Ebbert
2008-01-11 21:35 ` Jeff Garzik
2008-01-11 21:53 ` Chuck Ebbert [this message]
2008-01-11 23:21 ` Jeff Garzik
2008-01-11 23:28 ` Chuck Ebbert
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=4787E574.6020304@redhat.com \
--to=cebbert@redhat.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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).