From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, target-devel@vger.kernel.org
Subject: Re: [PATCH 3.6 1/2] target: remove pscsi_clear_cdb_lun
Date: Thu, 06 Sep 2012 11:58:05 -0700 [thread overview]
Message-ID: <1346957885.4162.509.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <1346944410-19850-2-git-send-email-pbonzini@redhat.com>
On Thu, 2012-09-06 at 17:13 +0200, Paolo Bonzini wrote:
> The purpose of this function is to clear a LUN set in the CDB, in case
> the initiator talking to us is speaking an old standards version.
> However, as things stand, pscsi_clear_cdb_lun has two problems. It
> will "deceive" the guest by clearing the LUN bits on initial
> commands (INQUIRY, TEST UNIT READY, etc.); but then it will let the
> LUN bits through on reads, which will likely fail due to protection not
> being enabled. Second, not all commands are properly filtered, in
> particular WRITE's WRPROTECT bits are cleared.
>
> This should be done by the fabric module rather than by PSCSI, if it
> knows such initiators may be lying around _and_ it can assume that its
> initiators do not really care about protection information. Nuke it
> from PSCSI.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
NAK. This code was originally added to prevent certain pSCSI HBAs from
going bonkers when they got a legacy SCSI LUN ID encoded within the CDB
(eg: the fabric LUN ID) that's different from the physical SCSI LUN ID
on an Parallel SCSI bus.
If there are more special cases where the legacy SCSI LUN ID bit-range
needs to be cleared than please add those missing bits, but I don't
think it's yet safe to remove this completely for pSCSI w/ older LLDs.
> drivers/target/target_core_pscsi.c | 26 --------------------------
> 1 files changed, 0 insertions(+), 26 deletions(-)
>
> diff --git a/drivers/target/target_core_pscsi.c b/drivers/target/target_core_pscsi.c
> index 5f7151d..a0fb2c3 100644
> --- a/drivers/target/target_core_pscsi.c
> +++ b/drivers/target/target_core_pscsi.c
> @@ -1031,30 +1031,6 @@ fail:
> return -ENOMEM;
> }
>
> -/*
> - * Clear a lun set in the cdb if the initiator talking to use spoke
> - * and old standards version, as we can't assume the underlying device
> - * won't choke up on it.
> - */
> -static inline void pscsi_clear_cdb_lun(unsigned char *cdb)
> -{
> - switch (cdb[0]) {
> - case READ_10: /* SBC - RDProtect */
> - case READ_12: /* SBC - RDProtect */
> - case READ_16: /* SBC - RDProtect */
> - case SEND_DIAGNOSTIC: /* SPC - SELF-TEST Code */
> - case VERIFY: /* SBC - VRProtect */
> - case VERIFY_16: /* SBC - VRProtect */
> - case WRITE_VERIFY: /* SBC - VRProtect */
> - case WRITE_VERIFY_12: /* SBC - VRProtect */
> - case MAINTENANCE_IN: /* SPC - Parameter Data Format for SA RTPG */
> - break;
> - default:
> - cdb[1] &= 0x1f; /* clear logical unit number */
> - break;
> - }
> -}
> -
> static int pscsi_parse_cdb(struct se_cmd *cmd)
> {
> unsigned char *cdb = cmd->t_task_cdb;
> @@ -1067,8 +1043,6 @@ static int pscsi_parse_cdb(struct se_cmd *cmd)
> return -EINVAL;
> }
>
> - pscsi_clear_cdb_lun(cdb);
> -
> /*
> * For REPORT LUNS we always need to emulate the response, for everything
> * else the default for pSCSI is to pass the command to the underlying
next prev parent reply other threads:[~2012-09-06 18:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-06 15:13 [PATCH 3.6 0/2] More PSCSI fixes Paolo Bonzini
2012-09-06 15:13 ` [PATCH 3.6 1/2] target: remove pscsi_clear_cdb_lun Paolo Bonzini
2012-09-06 18:58 ` Nicholas A. Bellinger [this message]
2012-09-06 20:51 ` Paolo Bonzini
2012-09-07 3:22 ` Nicholas A. Bellinger
2012-09-07 11:51 ` Paolo Bonzini
2012-09-07 17:52 ` Nicholas A. Bellinger
2012-09-06 15:13 ` [PATCH 3.6 2/2] target: use a bounce buffer in transport_kmap_data_sg for 0 or 1-page sglist Paolo Bonzini
2012-09-06 19:29 ` Nicholas A. Bellinger
2012-09-06 20:58 ` Paolo Bonzini
2012-09-07 3:35 ` Nicholas A. Bellinger
2012-09-07 12:01 ` Paolo Bonzini
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=1346957885.4162.509.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=target-devel@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).