public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Sagi Grimberg <sagig@mellanox.com>,
	linux-scsi@vger.kernel.org, target-devel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Bart Van Assche <bart.vanassche@sandisk.com>,
	Mike Christie <michaelc@cs.wisc.edu>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	"Nicholas A. Bellinger" <nab@linux-iscsi.org>
Subject: Re: [PATCH v1 3/4] target: Return descriptor format sense data in case the LU spans 64bit sectors
Date: Wed, 15 Jul 2015 10:06:05 +0200	[thread overview]
Message-ID: <55A6146D.50602@suse.de> (raw)
In-Reply-To: <1436946939-19415-4-git-send-email-sagig@mellanox.com>

On 07/15/2015 09:55 AM, Sagi Grimberg wrote:
> In case a LU spans 64bit sectors, fixed size sense data information
> field is only 32 bits which means the sector information will be truncated.
> 
> Thus, if the LU spans 64bit sectors, use descriptor format sense data to
> correctly report sector information.
> 
> Reported-by: Christoph Hellwig <hch@lst.de>
> Signed-off-by: Sagi Grimberg <sagig@mellanox.com>
> ---
>  drivers/target/target_core_hba.c       |  5 +++++
>  drivers/target/target_core_spc.c       | 12 +++++++++---
>  drivers/target/target_core_transport.c |  3 ++-
>  include/target/target_core_backend.h   |  2 ++
>  4 files changed, 18 insertions(+), 4 deletions(-)
> 
We should eventually move to have the D_SENSE parameter changeable,
But in the meantime:

Reviewed-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		               zSeries & Storage
hare@suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-07-15  8:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15  7:55 [PATCH v1 0/4] Descriptor format sense data Sagi Grimberg
2015-07-15  7:55 ` [PATCH v1 1/4] scsi: Fix wrong additional sense length in descriptor format Sagi Grimberg
2015-07-15  8:27   ` Christoph Hellwig
2015-07-15  7:55 ` [PATCH v1 2/4] scsi: Protect against buffer possible overflow in scsi_set_sense_information Sagi Grimberg
2015-07-15  8:29   ` Christoph Hellwig
2015-07-15  7:55 ` [PATCH v1 3/4] target: Return descriptor format sense data in case the LU spans 64bit sectors Sagi Grimberg
2015-07-15  8:06   ` Hannes Reinecke [this message]
2015-07-15  8:29   ` Christoph Hellwig
2015-07-15 14:07   ` Bart Van Assche
2015-07-16  0:34   ` Martin K. Petersen
2015-07-15  7:55 ` [PATCH v1 4/4] libiscsi: Use scsi helper to set information descriptor Sagi Grimberg
2015-07-15  8:07   ` Hannes Reinecke
2015-07-15  8:30   ` Christoph Hellwig
2015-07-16  0:33   ` Martin K. Petersen
2015-07-24  5:59 ` [PATCH v1 0/4] Descriptor format sense data Nicholas A. Bellinger

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=55A6146D.50602@suse.de \
    --to=hare@suse.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=bart.vanassche@sandisk.com \
    --cc=hch@infradead.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=michaelc@cs.wisc.edu \
    --cc=nab@linux-iscsi.org \
    --cc=sagig@mellanox.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