From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Vladislav Bolkhovitin <vst@vlnb.net>,
linux-scsi@vger.kernel.org
Subject: Re: T10-PI: Getting failed tag info
Date: Tue, 06 Jan 2015 18:49:50 -0500 [thread overview]
Message-ID: <yq1fvbn8o69.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20141230121542.GF32187@infradead.org> (Christoph Hellwig's message of "Tue, 30 Dec 2014 04:15:42 -0800")
>>>>> "Christoph" == Christoph Hellwig <hch@infradead.org> writes:
Christoph> But those extensions require new structures to pass in the PI
Christoph> info anyway..
Yep. But I still don't see why that warrants having a parallel error
passing infrastructure in the kernel to handle data integrity
errors. What does that buy us?
I agree with not leaking any of the new errors to unsuspecting
applications and only passing them out if the caller has explicitly
enabled DIX.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2015-01-06 23:50 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
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 [this message]
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=yq1fvbn8o69.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=vst@vlnb.net \
/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