From: hare@kernel.org
To: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCHv4 0/3] nvme: enable retries for authentication commands
Date: Mon, 29 Jan 2024 07:39:44 +0100 [thread overview]
Message-ID: <20240129063948.3105-1-hare@kernel.org> (raw)
From: Hannes Reinecke <hare@suse.de>
Hi all,
authentitication commands are normal NVMe commands, and should be retried
if returned with a status where the DNR bit is not set. But instead of
having the caller retry the commaand this patchset enables the function
__nvme_submit_sync_cmd() to not set the FASTFAIL flag in the request,
thereby making the functionality generally available.
As usual, comments and reviews are welcome.
Changes to v3:
- Modify patch description as suggested by Christoph
Hannes Reinecke (3):
nvme-auth: open-code single-use macros
nvme: change __nvme_submit_sync_cmd() calling conventions
nvme: enable retries for authentication commands
drivers/nvme/host/auth.c | 17 ++++++++---------
drivers/nvme/host/core.c | 21 ++++++++++++++-------
drivers/nvme/host/fabrics.c | 18 +++++++++++-------
drivers/nvme/host/nvme.h | 19 +++++++++++++++++--
4 files changed, 50 insertions(+), 25 deletions(-)
--
2.35.3
next reply other threads:[~2024-01-29 6:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-29 6:39 hare [this message]
2024-01-29 6:39 ` [PATCH 1/3] nvme-auth: open-code single-use macros hare
2024-01-29 20:00 ` Sagi Grimberg
2024-01-29 6:39 ` [PATCH 2/3] nvme: change __nvme_submit_sync_cmd() calling conventions hare
2024-01-29 20:00 ` Sagi Grimberg
2024-01-29 6:39 ` [PATCH 2/3] nvme: simplify " hare
2024-01-29 20:01 ` Sagi Grimberg
2024-01-29 6:39 ` [PATCH 3/3] nvme: enable retries for authentication commands hare
2024-01-29 7:10 ` Christoph Hellwig
2024-01-29 20:01 ` Sagi Grimberg
2024-02-01 0:29 ` [PATCHv4 0/3] " Keith Busch
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=20240129063948.3105-1-hare@kernel.org \
--to=hare@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@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;
as well as URLs for NNTP newsgroup(s).