From: Christoph Hellwig <hch@lst.de>
To: Gleb Chesnokov <gleb.chesnokov@scst.dev>
Cc: linux-nvme@lists.infradead.org, sagi@grimberg.me, kch@nvidia.com,
kbusch@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvmet: report backend transport errors as path errors
Date: Fri, 20 Nov 2026 18:56:58 +0100 [thread overview]
Message-ID: <20261120175658.GD1622@lst.de> (raw)
In-Reply-To: <0099f610-a48b-4557-8515-e4df444262e8@scst.dev>
On Fri, Nov 13, 2026 at 02:02:47PM +0300, Gleb Chesnokov wrote:
> The block backend maps BLK_STS_TRANSPORT to NVME_SC_INTERNAL with DNR
> set. This discards the backend's transport error classification. A Linux
> native multipath host completes the request before considering path
> failover, even if another controller can still access the namespace.
>
> Map BLK_STS_TRANSPORT to NVME_SC_INTERNAL_PATH_ERROR without DNR instead.
> The transport failure is behind the controller, so report an internal
> path error rather than a host path error. Associate the error log entry
> with the namespace, as for the existing access-denied status.
>
> This allows otherwise retryable native multipath requests to reach path
> error handling.
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2026-11-20 17:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 11:02 [PATCH] nvmet: report backend transport errors as path errors Gleb Chesnokov
2026-11-20 17:56 ` 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=20261120175658.GD1622@lst.de \
--to=hch@lst.de \
--cc=gleb.chesnokov@scst.dev \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.