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/2] nvme-auth: avoid locking during authentication
Date: Fri, 28 Oct 2022 15:50:25 +0200 [thread overview]
Message-ID: <20221028135027.116044-1-hare@suse.de> (raw)
Hi all,
blktests have uncovered a possible locking issue in the authentication
code. These patches rework the authentication context handling to
avoid long-running allocations and switch over to using xarray.
As usual, comments and reviews are welcome.
Hannes Reinecke (2):
nvme-auth: allocate authentication buffer only during transaction
nvme-auth: use xarray instead of linked list
drivers/nvme/host/auth.c | 163 +++++++++++++++++++++------------------
drivers/nvme/host/nvme.h | 3 +-
2 files changed, 88 insertions(+), 78 deletions(-)
--
2.35.3
next reply other threads:[~2022-10-28 13:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 13:50 Hannes Reinecke [this message]
2022-10-28 13:50 ` [PATCH 1/2] nvme-auth: allocate authentication buffer only during transaction Hannes Reinecke
2022-10-30 7:52 ` Christoph Hellwig
2022-10-31 17:46 ` Hannes Reinecke
2022-10-28 13:50 ` [PATCH 2/2] nvme-auth: use xarray instead of linked list Hannes Reinecke
2022-10-30 8:00 ` Christoph Hellwig
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=20221028135027.116044-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 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).