From: James Bottomley <James.Bottomley@suse.de>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: jaxboe@fusionio.com, linux-scsi@vger.kernel.org, Sathya.Prakash@lsi.com
Subject: Re: [PATCH] scsi: fix scsi_get_lba helper function for pc command
Date: Wed, 02 Jun 2010 09:07:08 -0500 [thread overview]
Message-ID: <1275487628.2799.18.camel@mulgrave.site> (raw)
In-Reply-To: <20100602163313S.fujita.tomonori@lab.ntt.co.jp>
On Wed, 2010-06-02 at 16:33 +0900, FUJITA Tomonori wrote:
> This fixes scsi_get_lba() helper function for PC commands.
>
> Only the block layer is supposed to touch rq->__sector. We could
> create a new accessor for it. But it seems overdoing a bit? Jens?
>
> =
> From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> Subject: [PATCH] scsi: fix scsi_get_lba helper function for pc command
>
> scsi_get_lba() can be used to get the lba info from
> scsi_cmnd. scsi_get_lba() gets the lba info from rq->__sector so
> scsi_get_lba() returns a bogus value for PC commands (we don't use
> rq->__sector for PC commands).
>
> This patch sets rq->__sector in scsi_setup_blk_pc_cmnd() so that
> scsi_get_lba() works with PC commands.
>
> scsi_get_data_transfer_info() is taken from
> scsi_debug. scsi_get_data_transfer_info() looks useful for some
> (scsi_debug, scsi_trace, libata, etc). So I export it. I'll convert
> them to use scsi_get_data_transfer_info().
>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> ---
> drivers/scsi/scsi_lib.c | 54 +++++++++++++++++++++++++++++++++++++++++++++-
> include/scsi/scsi_cmnd.h | 4 +++
> 2 files changed, 57 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
> index 1646fe7..b9b7f40 100644
> --- a/drivers/scsi/scsi_lib.c
> +++ b/drivers/scsi/scsi_lib.c
> @@ -19,6 +19,7 @@
> #include <linux/delay.h>
> #include <linux/hardirq.h>
> #include <linux/scatterlist.h>
> +#include <asm/unaligned.h>
>
> #include <scsi/scsi.h>
> #include <scsi/scsi_cmnd.h>
> @@ -69,6 +70,52 @@ struct kmem_cache *scsi_sdb_cache;
>
> static void scsi_run_queue(struct request_queue *q);
>
> +int scsi_get_data_transfer_info(unsigned char *cmd, unsigned long long *lba,
> + unsigned int *num, unsigned int *ei_lba)
> +{
> + int ret = 0;
> +
> + switch (*cmd) {
> + case VARIABLE_LENGTH_CMD:
> + *lba = get_unaligned_be64(&cmd[12]);
> + *num = get_unaligned_be32(&cmd[28]);
> + *ei_lba = get_unaligned_be32(&cmd[20]);
> + break;
You can't do this ... unless you know the format of the command. For
instance, if you knew this was a 32 byte CDB, then SPC does define where
the LBA is.
> + case WRITE_16:
> + case READ_16:
> + case VERIFY_16:
> + case WRITE_SAME_16:
> + *lba = get_unaligned_be64(&cmd[2]);
> + *num = get_unaligned_be32(&cmd[10]);
> + break;
> + case WRITE_12:
> + case READ_12:
> + case VERIFY_12:
> + *lba = get_unaligned_be32(&cmd[2]);
> + *num = get_unaligned_be32(&cmd[6]);
> + break;
> + case WRITE_10:
> + case READ_10:
> + case XDWRITEREAD_10:
> + case VERIFY:
> + case WRITE_SAME:
> + *lba = get_unaligned_be32(&cmd[2]);
> + *num = get_unaligned_be16(&cmd[7]);
> + break;
> + case WRITE_6:
> + case READ_6:
> + *lba = (u32)cmd[3] | (u32)cmd[2] << 8 |
> + (u32)(cmd[1] & 0x1f) << 16;
> + *num = (0 == cmd[4]) ? 256 : cmd[4];
> + break;
I really wouldn't do it like this because there are going to be
unexpected gaps. What about using the CDB groups instead? Each CDB
group has a well defined location for the LBA. The only problem is the
16 byte commands group because they have two forms: ordinary and long
LBA.
James
next prev parent reply other threads:[~2010-06-02 14:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 7:33 [PATCH] scsi: fix scsi_get_lba helper function for pc command FUJITA Tomonori
2010-06-02 8:14 ` Boaz Harrosh
2010-06-02 8:39 ` FUJITA Tomonori
2010-06-02 8:54 ` Boaz Harrosh
2010-06-02 9:05 ` FUJITA Tomonori
2010-06-02 9:23 ` Boaz Harrosh
2010-06-02 13:13 ` Martin K. Petersen
2010-06-03 10:59 ` FUJITA Tomonori
2010-06-03 11:03 ` Prakash, Sathya
2010-06-02 14:07 ` James Bottomley [this message]
2010-06-02 14:55 ` Douglas Gilbert
2010-06-03 11:18 ` FUJITA Tomonori
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=1275487628.2799.18.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=Sathya.Prakash@lsi.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jaxboe@fusionio.com \
--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