From: Ming Lei <ming.lei@redhat.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org, Omar Sandoval <osandov@fb.com>,
linux-block@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH] block/028: check if T10 verification fails
Date: Sat, 27 Apr 2019 11:29:39 +0800 [thread overview]
Message-ID: <20190427032938.GA825@ming.t460p> (raw)
In-Reply-To: <20190427012449.GC178347@magnolia>
On Fri, Apr 26, 2019 at 06:24:49PM -0700, Darrick J. Wong wrote:
> On Sat, Apr 27, 2019 at 06:16:32AM +0800, Ming Lei wrote:
> > On Fri, Apr 26, 2019 at 07:57:11AM -0700, Christoph Hellwig wrote:
> > > On Fri, Apr 26, 2019 at 10:39:37AM +0800, Ming Lei wrote:
> > > > When T10 verification fails, the error code of BLK_STS_PROTECTION
> > > > may not be propagated to user space, see mpage_end_io().
> > >
> > > Well, we should probably fix that instead of papering over it..
> >
> > That might be a big change, and not sure when they can be fixed
> > completely.
> >
> > This patch at least can expose the issue to user first.
>
> I don't see a patch anywhere ... ?
It is one blktest patch, please see the following link:
https://lore.kernel.org/linux-block/20190427012449.GC178347@magnolia/T/#t
Thanks,
Ming
prev parent reply other threads:[~2019-04-27 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190426023937.19584-1-ming.lei@redhat.com>
[not found] ` <20190426145711.GA12338@infradead.org>
2019-04-26 22:16 ` [PATCH] block/028: check if T10 verification fails Ming Lei
2019-04-27 1:24 ` Darrick J. Wong
2019-04-27 3:29 ` Ming Lei [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=20190427032938.GA825@ming.t460p \
--to=ming.lei@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=osandov@fb.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).