From: Hannes Reinecke <hare@suse.de>
To: Justin Tee <justintee8345@gmail.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: jsmart2021@gmail.com, justin.tee@broadcom.com,
Daniel Wagner <wagi@kernel.org>
Subject: Re: [PATCH 1/1] nvme-fabrics: add ENOKEY to no retry criteria for authentication failures
Date: Tue, 18 Nov 2025 08:01:10 +0100 [thread overview]
Message-ID: <c2b9fb9c-440d-4e41-b4e8-7428fcf9c2ca@suse.de> (raw)
In-Reply-To: <20251117184343.97605-1-justintee8345@gmail.com>
On 11/17/25 19:43, Justin Tee wrote:
> With authentication, in addition to EKEYREJECTED there is also no point in
> retrying reconnects when status is ENOKEY. Thus, add -ENOKEY as another
> criteria to determine when to stop retries.
>
> Cc: Daniel Wagner <wagi@kernel.org>
> Cc: Hannes Reinecke <hare@suse.de>
> Closes: https://lore.kernel.org/linux-nvme/20250829-nvme-fc-sync-v3-0-d69c87e63aee@kernel.org/
> Signed-off-by: Justin Tee <justintee8345@gmail.com>
> ---
> drivers/nvme/host/fabrics.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/nvme/host/fabrics.c b/drivers/nvme/host/fabrics.c
> index 3d4d6d8e88c4..fb7765bf0cdf 100644
> --- a/drivers/nvme/host/fabrics.c
> +++ b/drivers/nvme/host/fabrics.c
> @@ -594,7 +594,7 @@ bool nvmf_should_reconnect(struct nvme_ctrl *ctrl, int status)
> if (status > 0 && (status & NVME_STATUS_DNR))
> return false;
>
> - if (status == -EKEYREJECTED)
> + if (status == -EKEYREJECTED || status == -ENOKEY)
> return false;
>
> if (ctrl->opts->max_reconnects == -1 ||
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2025-11-18 7:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 18:43 [PATCH 1/1] nvme-fabrics: add ENOKEY to no retry criteria for authentication failures Justin Tee
2025-11-18 7:01 ` Hannes Reinecke [this message]
2025-11-24 10:26 ` Daniel Wagner
2025-11-25 0:57 ` Justin Tee
2025-11-25 10:34 ` Daniel Wagner
2025-11-26 8:12 ` Daniel Wagner
2025-11-24 19:36 ` Keith Busch
2025-11-30 23:05 ` Sagi Grimberg
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=c2b9fb9c-440d-4e41-b4e8-7428fcf9c2ca@suse.de \
--to=hare@suse.de \
--cc=jsmart2021@gmail.com \
--cc=justin.tee@broadcom.com \
--cc=justintee8345@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=wagi@kernel.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.