From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Sagi Grimberg <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCH 0/6] nvme-auth: use xarray and minor fixes
Date: Wed, 2 Nov 2022 08:52:18 +0100 [thread overview]
Message-ID: <20221102075224.70869-1-hare@suse.de> (raw)
Hi all,
this patchset moves the dhchap context allocation to an xarray to avoid
locking issues uncovered by blktests. But during review of the original patch
several issues were pointed out (like allocating the transaction buffer
even if the transaction is finished), and I've found several other issues, too.
So I've decided to wrap them all up in a patchset.
So as usual, comments and reviews are welcome.
Hannes Reinecke (6):
nvme-auth: allocate authentication buffer only during transaction
nvme-auth: do not queue authentication if the queue is not live
nvme-auth: use xarray instead of linked list
nvme-auth: return real error instead of NVME_SC_AUTH_REQUIRED
nvme-auth: set DNR bit on non-retryable errors
nvme-auth: use a define for chap buffer size
drivers/nvme/host/auth.c | 199 +++++++++++++++++++-----------------
drivers/nvme/host/fabrics.c | 2 -
drivers/nvme/host/nvme.h | 2 +-
3 files changed, 107 insertions(+), 96 deletions(-)
--
2.35.3
next reply other threads:[~2022-11-02 7:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 7:52 Hannes Reinecke [this message]
2022-11-02 7:52 ` [PATCH 1/6] nvme-auth: allocate authentication buffer only during transaction Hannes Reinecke
2022-11-03 20:01 ` Sagi Grimberg
2022-11-04 6:49 ` Hannes Reinecke
2022-11-04 6:55 ` Christoph Hellwig
2022-11-02 7:52 ` [PATCH 2/6] nvme-auth: do not queue authentication if the queue is not live Hannes Reinecke
2022-11-03 21:19 ` Sagi Grimberg
2022-11-04 6:54 ` Hannes Reinecke
2022-11-02 7:52 ` [PATCH 3/6] nvme-auth: use xarray instead of linked list Hannes Reinecke
2022-11-02 8:03 ` Christoph Hellwig
2022-11-02 8:52 ` Hannes Reinecke
2022-11-02 8:54 ` Christoph Hellwig
2022-11-03 21:20 ` Sagi Grimberg
2022-11-04 6:57 ` Hannes Reinecke
2022-11-02 7:52 ` [PATCH 4/6] nvme-auth: return real error instead of NVME_SC_AUTH_REQUIRED Hannes Reinecke
2022-11-02 7:52 ` [PATCH 5/6] nvme-auth: set DNR bit on non-retryable errors Hannes Reinecke
2022-11-02 8:02 ` Christoph Hellwig
2022-11-02 8:40 ` Hannes Reinecke
2022-11-02 7:52 ` [PATCH 6/6] nvme-auth: use a define for chap buffer size Hannes Reinecke
2022-11-03 21:22 ` 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=20221102075224.70869-1-hare@suse.de \
--to=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 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.