From: Vladislav Bolkhovitin <vst@vlnb.net>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: T10-PI: Getting failed tag info
Date: Fri, 12 Dec 2014 19:57:05 -0800 [thread overview]
Message-ID: <548BB911.6090905@vlnb.net> (raw)
In-Reply-To: <yq1r3w5blys.fsf@sermon.lab.mkp.net>
Martin K. Petersen wrote on 12/11/2014 07:12 PM:
>>>>>> "Vlad" == Vladislav Bolkhovitin <vst@vlnb.net> writes:
> Vlad> We are currently developing a SCSI target system with T10-PI. We
> Vlad> are using block integrity interface and found a problem that this
> Vlad> interface fundamentally can not pass Oracle T10-PI certification
> Vlad> tests. Those tests require to receive on the initiator side
> Vlad> information about which particular tag failed the target checks,
> Vlad> but the block integrity interface does not preserve this
> Vlad> information, hence the target can not deliver it to the initiator
> Vlad> => certification failure. The storage provides the right sense,
> Vlad> but then in scsi_io_completion() it is dropped and replaced by a
> Vlad> single EILSEQ.
>
> Vlad> What would be the best way to fix that? By making a patch
> Vlad> introducing new -EXXXXXX error codes for the PI errors?
>
> I posted such a patch a while back. We use that in our qualification
> tooling to ensure that the right things are reported when a PI error is
> injected at various places in the stack.
Thanks, this is exactly what is needed.
Reviewed-by: Vladislav Bolkhovitin <vst@vlnb.net>
> One thing that needs to be done is to make returning these new errors to
> userland conditional on !BIP_BLOCK_INTEGRITY. I'll put that on my list.
Ever without it this patch is quite valuable.
Vlad
next prev parent reply other threads:[~2014-12-13 3:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 4:58 T10-PI: Getting failed tag info Vladislav Bolkhovitin
2014-12-12 3:12 ` Martin K. Petersen
2014-12-12 23:15 ` Nicholas A. Bellinger
2014-12-16 0:30 ` Martin K. Petersen
2014-12-13 3:57 ` Vladislav Bolkhovitin [this message]
2014-12-16 0:32 ` Martin K. Petersen
2014-12-15 8:18 ` Christoph Hellwig
2014-12-16 0:45 ` Martin K. Petersen
2014-12-30 12:15 ` Christoph Hellwig
2015-01-06 23:49 ` Martin K. Petersen
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=548BB911.6090905@vlnb.net \
--to=vst@vlnb.net \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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.