From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme: make nvme error status codes converted to errno detailed
Date: Thu, 30 Mar 2017 10:20:38 -0700 [thread overview]
Message-ID: <20170330172038.GA6037@infradead.org> (raw)
In-Reply-To: <20170330172236.GG20181@localhost.localdomain>
On Thu, Mar 30, 2017@01:22:37PM -0400, Keith Busch wrote:
> I don't see a problem having more appropriate errno's here. The block
> layer looks okay to accept any value, and the spec folks might be happy
> to see their thought out status codes don't all become EIO. :)
The block layer accepts all and treats a few magically. That's why I
want to get rid of errno values in the block layer entirely and replace
the with a few status codes that make the special casing obvious.
> But just so we all know, the majority of those statuses are only possible
> to encounter with passthrough, and those are not translated to errno.
Exactly.
prev parent reply other threads:[~2017-03-30 17:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 10:08 [PATCH] nvme: make nvme error status codes converted to errno detailed Guan Junxiong
2017-03-29 17:39 ` Sagi Grimberg
2017-03-30 8:05 ` guanjunxiong
2017-03-30 8:11 ` Christoph Hellwig
2017-03-30 11:32 ` guanjunxiong
2017-03-30 17:22 ` Keith Busch
2017-03-30 17:20 ` Christoph Hellwig [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=20170330172038.GA6037@infradead.org \
--to=hch@infradead.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.