From: Dan Carpenter <error27@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: oe-kbuild@lists.linux.dev, Sagi Grimberg <sagi@grimberg.me>,
lkp@intel.com, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: drivers/nvme/host/auth.c:950 nvme_auth_init_ctrl() warn: missing error code? 'ret'
Date: Fri, 23 Dec 2022 19:21:49 +0300 [thread overview]
Message-ID: <Y6XVnWCNx6cB7Itw@kadam> (raw)
In-Reply-To: <20221223154754.GA30339@lst.de>
On Fri, Dec 23, 2022 at 04:47:54PM +0100, Christoph Hellwig wrote:
> diff --git a/drivers/nvme/host/auth.c b/drivers/nvme/host/auth.c
> index bb0abbe4491cdc..c808652966a94f 100644
> --- a/drivers/nvme/host/auth.c
> +++ b/drivers/nvme/host/auth.c
> @@ -943,16 +943,19 @@ int nvme_auth_init_ctrl(struct nvme_ctrl *ctrl)
> INIT_WORK(&ctrl->dhchap_auth_work, nvme_ctrl_auth_work);
> if (!ctrl->opts)
> return 0;
> - ret = nvme_auth_generate_key(ctrl->opts->dhchap_secret,
> - &ctrl->host_key);
> - if (ret)
> - return ret;
> - ret = nvme_auth_generate_key(ctrl->opts->dhchap_ctrl_secret,
> - &ctrl->ctrl_key);
> - if (ret)
> +
> + ctrl->host_key = nvme_auth_generate_key(ctrl->opts->dhchap_secret);
> + if (IS_ERR(ctrl->host_key)) {
> + ret = PTR_ERR(ctrl->host_key);
> + goto out;
> + }
> + ctrl->ctrl_key = nvme_auth_generate_key(ctrl->opts->dhchap_ctrl_secret);
> + if (IS_ERR(ctrl->ctrl_key)) {
> + ret = PTR_ERR(ctrl->ctrl_key);
> goto err_free_dhchap_secret;
> + }
>
> - if (!ctrl->opts->dhchap_secret && !ctrl->opts->dhchap_ctrl_secret)
> + if (!ctrl->host_key && !ctrl->ctrl_key)
> return ret;
ret is uninitialized now.
regards,
dan carpenter
next prev parent reply other threads:[~2022-12-23 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 11:03 drivers/nvme/host/auth.c:950 nvme_auth_init_ctrl() warn: missing error code? 'ret' Dan Carpenter
2022-12-23 15:47 ` Christoph Hellwig
2022-12-23 16:21 ` Dan Carpenter [this message]
2022-12-23 16:42 ` Christoph Hellwig
2022-12-25 10:36 ` Sagi Grimberg
2022-12-27 17:53 ` Dan Carpenter
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=Y6XVnWCNx6cB7Itw@kadam \
--to=error27@gmail.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
--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