From: Tom Rix <trix@redhat.com>
To: Peter Gonda <pgonda@google.com>
Cc: brijesh.singh@amd.com, thomas.lendacky@amd.com,
john.allen@amd.com, herbert@gondor.apana.org.au,
davem@davemloft.net, nathan@kernel.org, ndesaulniers@google.com,
rientjes@google.com, marcorr@google.com,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH] crypto: initialize error
Date: Tue, 10 Jan 2023 08:48:33 -0800 [thread overview]
Message-ID: <ecd0c7f2-f82c-845f-b1fe-a7d3bf495bb1@redhat.com> (raw)
In-Reply-To: <CAMkAt6oqBH35=moST5nO_BXwc8k0M4h_8TvT9H6outR9vOw5qg@mail.gmail.com>
On 1/10/23 8:27 AM, Peter Gonda wrote:
> On Tue, Jan 10, 2023 at 9:18 AM Tom Rix <trix@redhat.com> wrote:
>> clang static analysis reports this problem
>> drivers/crypto/ccp/sev-dev.c:1347:3: warning: 3rd function call
>> argument is an uninitialized value [core.CallAndMessage]
>> dev_err(sev->dev, "SEV: failed to INIT error %#x, rc %d\n",
>> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>> __sev_platform_init_locked() can return without setting the
>> error parameter, causing the dev_err() to report a gargage
> garbage
ok
>
>> value.
>>
>> Fixes: 3d725965f836 ("crypto: ccp - Add SEV_INIT_EX support")
> Should this be: 'Fixes: 200664d5237f ("crypto: ccp: Add Secure
> Encrypted Virtualization (SEV) command support")'
>
> Since in that patch an uninitialized error can be printed?
It was a bit of a toss up on who is at fault. This is fine, i'll change
this as well.
Thanks
Tom
> +void psp_pci_init(void)
> +{
> + struct sev_user_data_status *status;
> + struct sp_device *sp;
> + int error, rc;
> +
> + sp = sp_get_psp_master_device();
> + if (!sp)
> + return;
> +
> + psp_master = sp->psp_data;
> +
> + /* Initialize the platform */
> + rc = sev_platform_init(&error);
> + if (rc) {
> + dev_err(sp->dev, "SEV: failed to INIT error %#x\n", error);
> + goto err;
> + }
>
>
> ...
>
> +static int __sev_platform_init_locked(int *error)
> +{
> + struct psp_device *psp = psp_master;
> + int rc = 0;
> +
> + if (!psp)
> + return -ENODEV;
> +
> + if (psp->sev_state == SEV_STATE_INIT)
> + return 0;
>
>
> So if !psp an uninitialized error is printed?
>
>> Signed-off-by: Tom Rix <trix@redhat.com>
>> ---
>> drivers/crypto/ccp/sev-dev.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/crypto/ccp/sev-dev.c b/drivers/crypto/ccp/sev-dev.c
>> index 56998bc579d6..643cccc06a0b 100644
>> --- a/drivers/crypto/ccp/sev-dev.c
>> +++ b/drivers/crypto/ccp/sev-dev.c
>> @@ -1307,7 +1307,7 @@ EXPORT_SYMBOL_GPL(sev_issue_cmd_external_user);
>> void sev_pci_init(void)
>> {
>> struct sev_device *sev = psp_master->sev_data;
>> - int error, rc;
>> + int error = 0, rc;
>>
>> if (!sev)
>> return;
>> --
>> 2.27.0
>>
next prev parent reply other threads:[~2023-01-10 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 16:18 Tom Rix
2023-01-10 16:27 ` Peter Gonda
2023-01-10 16:48 ` Tom Rix [this message]
2023-01-10 16:53 ` Peter Gonda
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=ecd0c7f2-f82c-845f-b1fe-a7d3bf495bb1@redhat.com \
--to=trix@redhat.com \
--cc=brijesh.singh@amd.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=marcorr@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=pgonda@google.com \
--cc=rientjes@google.com \
--cc=thomas.lendacky@amd.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®