From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@infradead.org>,
Sagi Grimberg <sagig@dev.mellanox.co.il>
Cc: Sagi Grimberg <sagig@mellanox.com>,
target-devel@vger.kernel.org, linux-scsi@vger.kernel.org,
"Nicholas A. Bellinger" <nab@linux-iscsi.org>,
Bart Van Assche <bart.vanassche@sandisk.com>
Subject: Re: [PATCH v3 5/5] target: Fix wrong setting of sense format for PI errors
Date: Wed, 08 Jul 2015 12:59:18 +0200 [thread overview]
Message-ID: <559D0286.4070202@suse.de> (raw)
In-Reply-To: <20150708104955.GA20842@infradead.org>
On 07/08/2015 12:49 PM, Christoph Hellwig wrote:
> On Wed, Jul 08, 2015 at 01:36:04PM +0300, Sagi Grimberg wrote:
>> We don't have any other information today, but sector is not the only
>> information that is requires a descriptor format, so maybe it will be a
>> bit awkward to condition the descriptor format on the sector info?
>
> The only reason why you'd want to support descriptor type sense data is
> because you need to add a second descriptor. If we have another case
> that needs descriptor sense data it'll also need to add that additional
> descriptor. So we'll need a conditional for it in the sense data
> generation anyway.
>
Actually it's controlled by the D_SENSE bit in the Control mode page
(that's bit[2] of byte 2 in the control mode page).
Which is currently set to '0', ie we will be returning fixed sense
information.
_If_ we were to report descriptor sense we will need to change that,
too.
And it's actually not true that you'd need descriptor sense to
encode the sector information; it'll be stored in the 'information'
section (byte 3-6) for fixed format sense.
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
next prev parent reply other threads:[~2015-07-08 10:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 13:15 [PATCH v3 0/5] Target sense data handling modifications Sagi Grimberg
2015-07-06 13:15 ` [PATCH v3 1/5] target: Inline transport_get_sense_codes() Sagi Grimberg
2015-07-06 13:15 ` [PATCH v3 2/5] target: Split transport_send_check_condition_and_sense() Sagi Grimberg
2015-07-08 10:15 ` Christoph Hellwig
2015-07-08 10:24 ` Sagi Grimberg
2015-07-06 13:15 ` [PATCH v3 3/5] scsi: Move sense handling routines to scsi_common Sagi Grimberg
2015-07-06 15:25 ` Bart Van Assche
2015-07-08 10:16 ` Christoph Hellwig
2015-07-06 13:15 ` [PATCH v3 4/5] target: Use scsi helpers to build the sense data correctly Sagi Grimberg
2015-07-08 10:17 ` Christoph Hellwig
2015-07-08 10:23 ` Sagi Grimberg
2015-07-06 13:15 ` [PATCH v3 5/5] target: Fix wrong setting of sense format for PI errors Sagi Grimberg
2015-07-06 15:28 ` Bart Van Assche
2015-07-06 16:14 ` Sagi Grimberg
2015-07-06 16:22 ` Bart Van Assche
2015-07-08 10:19 ` Christoph Hellwig
2015-07-08 10:36 ` Sagi Grimberg
2015-07-08 10:49 ` Christoph Hellwig
2015-07-08 10:59 ` Hannes Reinecke [this message]
2015-07-08 11:14 ` Sagi Grimberg
2015-07-08 12:59 ` Sagi Grimberg
2015-07-08 11:44 ` Christoph Hellwig
2015-07-08 12:02 ` Sagi Grimberg
2015-07-06 22:51 ` [PATCH v3 0/5] Target sense data handling modifications Nicholas A. Bellinger
2015-07-07 6:18 ` Sagi Grimberg
2015-07-07 6:48 ` 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=559D0286.4070202@suse.de \
--to=hare@suse.de \
--cc=bart.vanassche@sandisk.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=sagig@dev.mellanox.co.il \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.