From: Brian King <brking@us.ibm.com>
To: Brian King <brking@us.ibm.com>
Cc: jgarzik@pobox.com, linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 4/4] libata: Check per device max cdb length for SAS - drop
Date: Wed, 28 Jun 2006 23:53:21 -0500 [thread overview]
Message-ID: <44A35CC1.1030407@us.ibm.com> (raw)
In-Reply-To: <200606281330.k5SDUrOv021506@d03av04.boulder.ibm.com>
Brian King wrote:
> Since libata does not own any scsi_host struct for
> SAS attached SATA devices, libata cannot rely on scsi
> core checking the max_cmd_len. This patch adds additional
> checking into the SAS queuecommand path to prevent
> too large of a cdb from being issued to an ATA or ATAPI device.
I'd like to drop this patch from the series. This patch would end up
preventing ATA passthrough from working to ATA/ATAPI devices that
support < 16 byte CDBs.
Brian
prev parent reply other threads:[~2006-06-29 4:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 13:30 [PATCH 4/4] libata: Check per device max cdb length for SAS Brian King
2006-06-29 4:53 ` Brian King [this message]
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=44A35CC1.1030407@us.ibm.com \
--to=brking@us.ibm.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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).