From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
"James Bottomley" <James.Bottomley@hansenpartnership.com>,
linux-integrity <linux-integrity@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] tpm: fix error return code in tpm2_get_cc_attrs_tbl()
Date: Wed, 12 May 2021 09:12:26 +0800 [thread overview]
Message-ID: <b79b306a-71da-f655-3e68-11f1c9df4115@huawei.com> (raw)
In-Reply-To: <YJhI+lIt4devpAoS@kernel.org>
On 2021/5/10 4:41, Jarkko Sakkinen wrote:
> On Sat, May 08, 2021 at 10:54:44AM +0800, Zhen Lei wrote:
>> Fix to return a negative error code from the error handling
>> case instead of 0, as done elsewhere in this function.
>>
>> Fixes: 58472f5cd4f6("tpm: validate TPM 2.0 commands")
>> Reported-by: Hulk Robot <hulkci@huawei.com>
>> Signed-off-by: Zhen Lei <thunder.leizhen@huawei.com>
>
> In the commit message:
>
> 1. Instead of writing "a negative error code", write -EFAULT.
OK, I will change it.
> 2. Some explanation of the choice.
Do you mean why I choice error code -EFAULT? There's a similar one above this branch.
if (nr_commands > 0xFFFFF) {
rc = -EFAULT;
goto out;
}
>
>> ---
>> drivers/char/tpm/tpm2-cmd.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/char/tpm/tpm2-cmd.c b/drivers/char/tpm/tpm2-cmd.c
>> index eff1f12d981a..c84d23951219 100644
>> --- a/drivers/char/tpm/tpm2-cmd.c
>> +++ b/drivers/char/tpm/tpm2-cmd.c
>> @@ -656,6 +656,7 @@ int tpm2_get_cc_attrs_tbl(struct tpm_chip *chip)
>>
>> if (nr_commands !=
>> be32_to_cpup((__be32 *)&buf.data[TPM_HEADER_SIZE + 5])) {
>> + rc = -EFAULT;
>> tpm_buf_destroy(&buf);
>> goto out;
>> }
>> --
>> 2.25.1
>>
>>
>>
>
> Other than that looks good.
>
> /Jarkko
>
> .
>
next prev parent reply other threads:[~2021-05-12 1:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-08 2:54 Zhen Lei
2021-05-09 20:41 ` Jarkko Sakkinen
2021-05-12 1:12 ` Leizhen (ThunderTown) [this message]
2021-05-12 1:21 ` Jarkko Sakkinen
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=b79b306a-71da-f655-3e68-11f1c9df4115@huawei.com \
--to=thunder.leizhen@huawei.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/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®