From: Hannes Reinecke <hare@suse.de>
To: Sreeraj S Kurup <sreekuttan2156239@gmail.com>,
hare@kernel.org, hch@lst.de, kbusch@kernel.org, kch@nvidia.com,
sagi@grimberg.me
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH v4] nvmet: clean up DH group state on initialization failure
Date: Tue, 10 Nov 2026 14:05:25 +0100 [thread overview]
Message-ID: <2f0e8fe5-42b6-47d9-9bcd-c549544e099a@suse.de> (raw)
In-Reply-To: <20261110113502.3235-1-sreekuttan2156239@gmail.com>
On 11/10/26 12:35 PM, Sreeraj S Kurup wrote:
> nvmet_setup_dhgroup() leaves the DH transform and group ID
> initialized when private-key generation, public-key allocation,
> or public-key generation fails.
>
> A subsequent invocation with the same DH group incorrectly
> returns success because the existing transform and group ID
> are treated as proof of successful initialization.
>
> Release the transform and reset the group state on initialization
> failures so that subsequent attempts can properly retry setup.
>
> Fixes: 7a277c37d352 ("nvmet-auth: Diffie-Hellman key exchange support")
> Signed-off-by: Sreeraj S Kurup <sreekuttan2156239@gmail.com>
> ---
> v4:
> - Consolidate DH group error handling and clear stale key state
> when switching DH groups.
> v3:
> - Clear stale DH key state when crypto_alloc_kpp() fails during
> re-authentication.
> - Fix the error path when crypto_alloc_kpp() fails by returning
> the allocation error instead of incorrectly reporting success.
> v2:
> - Consolidate error handling in "nvmet_setup_dhgroup()" using
> a shared cleanup label to avoid duplicated teardown code.
> - Add Fixes trailer.
>
> drivers/nvme/target/auth.c | 67 +++++++++++++++++++++-----------------
> 1 file changed, 37 insertions(+), 30 deletions(-)
>
> diff --git a/drivers/nvme/target/auth.c b/drivers/nvme/target/auth.c
> index ccba84b1344e..681459b5db3b 100644
> --- a/drivers/nvme/target/auth.c
> +++ b/drivers/nvme/target/auth.c
> @@ -76,8 +76,11 @@ int nvmet_setup_dhgroup(struct nvmet_ctrl *ctrl, u8 dhgroup_id)
> return 0;
> }
> crypto_free_kpp(ctrl->dh_tfm);
> + kfree_sensitive(ctrl->dh_key);
> ctrl->dh_tfm = NULL;
> ctrl->dh_gid = 0;
> + ctrl->dh_key = NULL;
> + ctrl->dh_keysize = 0;
> }
>
> if (dhgroup_id == NVME_AUTH_DHGROUP_NULL)
> @@ -95,38 +98,42 @@ int nvmet_setup_dhgroup(struct nvmet_ctrl *ctrl, u8 dhgroup_id)
> __func__, ctrl->cntlid, dhgroup_id,
> PTR_ERR(ctrl->dh_tfm));
> ret = PTR_ERR(ctrl->dh_tfm);
> - ctrl->dh_tfm = NULL;
> - ctrl->dh_gid = 0;
> - } else {
> - ctrl->dh_gid = dhgroup_id;
> - pr_debug("%s: ctrl %d setup DH group %d\n",
> - __func__, ctrl->cntlid, ctrl->dh_gid);
> - ret = nvme_auth_gen_privkey(ctrl->dh_tfm, ctrl->dh_gid);
> - if (ret < 0) {
> - pr_debug("%s: ctrl %d failed to generate private key, err %d\n",
> - __func__, ctrl->cntlid, ret);
> - kfree_sensitive(ctrl->dh_key);
> - ctrl->dh_key = NULL;
> - return ret;
> - }
> - ctrl->dh_keysize = crypto_kpp_maxsize(ctrl->dh_tfm);
> - kfree_sensitive(ctrl->dh_key);
> - ctrl->dh_key = kzalloc(ctrl->dh_keysize, GFP_KERNEL);
> - if (!ctrl->dh_key) {
> - pr_warn("ctrl %d failed to allocate public key\n",
> - ctrl->cntlid);
> - return -ENOMEM;
> - }
> - ret = nvme_auth_gen_pubkey(ctrl->dh_tfm, ctrl->dh_key,
> - ctrl->dh_keysize);
> - if (ret < 0) {
> - pr_warn("ctrl %d failed to generate public key\n",
> - ctrl->cntlid);
> - kfree(ctrl->dh_key);
> - ctrl->dh_key = NULL;
> - }
> + goto err;
> + }
> +
> + ctrl->dh_gid = dhgroup_id;
> + pr_debug("%s: ctrl %d setup DH group %d\n",
> + __func__, ctrl->cntlid, ctrl->dh_gid);
> + ret = nvme_auth_gen_privkey(ctrl->dh_tfm, ctrl->dh_gid);
> + if (ret < 0) {
> + pr_debug("%s: ctrl %d failed to generate private key, err %d\n",
> + __func__, ctrl->cntlid, ret);
> + goto err;
> + }
> + ctrl->dh_keysize = crypto_kpp_maxsize(ctrl->dh_tfm);
> + ctrl->dh_key = kzalloc(ctrl->dh_keysize, GFP_KERNEL);
> + if (!ctrl->dh_key) {
> + pr_warn("ctrl %d failed to allocate public key\n",
> + ctrl->cntlid);
> + ret = -ENOMEM;
> + goto err;
> + }
> + ret = nvme_auth_gen_pubkey(ctrl->dh_tfm, ctrl->dh_key,
> + ctrl->dh_keysize);
> + if (ret < 0) {
> + pr_warn("ctrl %d failed to generate public key\n",
> + ctrl->cntlid);
> + goto err;
> }
>
> + return 0;
> +err:
> + kfree_sensitive(ctrl->dh_key);
> + ctrl->dh_key = NULL;
> + crypto_free_kpp(ctrl->dh_tfm);
> + ctrl->dh_tfm = NULL;
> + ctrl->dh_gid = 0;
> + ctrl->dh_keysize = 0;
> return ret;
> }
>
Still wonder if a helper wouldn't be better here.
But anyway.
Reviewed-by: Hannes Reinecke <hare@kernel.org>
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:[~2026-11-10 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 11:35 Sreeraj S Kurup
2026-11-10 13:05 ` Hannes Reinecke [this message]
2026-11-10 13:47 ` Sreeraj S Kurup
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=2f0e8fe5-42b6-47d9-9bcd-c549544e099a@suse.de \
--to=hare@suse.de \
--cc=hare@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=sreekuttan2156239@gmail.com \
/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
all inboxes | Powered by JetHome®