From: Sagi Grimberg <sagi@grimberg.me>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-nvme@lists.infradead.org, Keith Busch <kbusch@kernel.org>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH 0/6] nvme: a few nvme-auth fixes found during code browsing
Date: Tue, 25 Oct 2022 18:46:51 +0300 [thread overview]
Message-ID: <d8d87fd0-b217-0ba8-b94a-903db9bbf070@grimberg.me> (raw)
In-Reply-To: <20221025153224.GA24369@lst.de>
> The changes all look reasonable to me, but I think we really need to fix
> the grave locking bug in nvme_auth_reset before doing more changs in
> this area.
In the works... this is part one.
prev parent reply other threads:[~2022-10-25 15:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 13:43 [PATCH 0/6] nvme: a few nvme-auth fixes found during code browsing Sagi Grimberg
2022-10-25 13:43 ` [PATCH 1/6] nvme-auth: rename __nvme_auth_[reset|free] to nvme_auth[reset|free]_dhchap Sagi Grimberg
2022-10-25 17:18 ` Hannes Reinecke
2022-10-25 17:34 ` Chaitanya Kulkarni
2022-10-25 13:43 ` [PATCH 2/6] nvme-auth: remove symbol export from nvme_auth_reset Sagi Grimberg
2022-10-25 17:18 ` Hannes Reinecke
2022-10-25 17:34 ` Chaitanya Kulkarni
2022-10-25 13:43 ` [PATCH 3/6] nvme-auth: don't re-authenticate if the controller is not LIVE Sagi Grimberg
2022-10-25 17:22 ` Hannes Reinecke
2022-10-25 20:22 ` Sagi Grimberg
2022-10-25 13:43 ` [PATCH 4/6] nvme-auth: remove redundant buffer deallocations Sagi Grimberg
2022-10-25 17:23 ` Hannes Reinecke
2022-10-25 17:36 ` Chaitanya Kulkarni
2022-10-25 13:43 ` [PATCH 5/6] nvme-auth: don't ignore key generation failures when initializing ctrl keys Sagi Grimberg
2022-10-25 17:24 ` Hannes Reinecke
2022-10-25 13:43 ` [PATCH 6/6] nvme-auth: don't override ctrl keys before validation Sagi Grimberg
2022-10-25 17:25 ` Hannes Reinecke
2022-10-25 15:32 ` [PATCH 0/6] nvme: a few nvme-auth fixes found during code browsing Christoph Hellwig
2022-10-25 15:46 ` Sagi Grimberg [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=d8d87fd0-b217-0ba8-b94a-903db9bbf070@grimberg.me \
--to=sagi@grimberg.me \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.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 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).