mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: <linux-nvme@lists.infradead.org>,
	Gleb Chesnokov <gleb.chesnokov@scst.dev>
Cc: <hch@lst.de>, <sagi@grimberg.me>, <kch@nvidia.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvmet: report backend transport errors as path errors
Date: Fri, 20 Nov 2026 11:54:35 -0800	[thread overview]
Message-ID: <179520447586.200813.7403174515660179966.b4-ty@kernel.org> (raw)
In-Reply-To: <0099f610-a48b-4557-8515-e4df444262e8@scst.dev>

On Fri, 13 Nov 2026 14:02:47 +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.
> 
> [...]

Thanks, applied to nvme-7.5.

[1/1] nvmet: report backend transport errors as path errors
      commit: 3b90e37012c0c5297ccbd7b531287b943c818bba
--
Keith Busch <kbusch@kernel.org>


      parent reply	other threads:[~2026-11-20 19:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 11:02 Gleb Chesnokov
2026-11-20 17:56 ` Christoph Hellwig
2026-11-20 19:54 ` Keith Busch [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=179520447586.200813.7403174515660179966.b4-ty@kernel.org \
    --to=kbusch@kernel.org \
    --cc=gleb.chesnokov@scst.dev \
    --cc=hch@lst.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®