public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Baoli" <baoli.zhang@linux.intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Peter Huewe <peterhuewe@gmx.de>,
	Jarkko Sakkinen <jarkko@kernel.org>,
	Jason Gunthorpe <jgg@ziepe.ca>, Serge Hallyn <serge@hallyn.com>,
	Lili Li <lili.li@intel.com>,
	linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] tpm: restore timeout for key creation commands
Date: Mon, 13 Apr 2026 09:31:10 +0800	[thread overview]
Message-ID: <90a02329-5e95-4eb8-ac47-028690bf52b3@linux.intel.com> (raw)
In-Reply-To: <2f9f7dcf-7cea-46f8-8887-ac2495e12863@molgen.mpg.de>


On 4/10/2026 2:49 PM, Paul Menzel wrote:
> Dear Baoli,
>
>
> Thank you for your patch. Some formalities:
>
> Am 10.04.26 um 03:49 schrieb Baoli.Zhang:
>> After the per-command duration map was introduced, TPM2 key creation
>> commands (`CREATE_PRIMARY`, `CREATE`, `CREATE_LOADED`) were limited to
>> 30 seconds.
>>
>> On some platforms this is not sufficient and key creation can time out.
>> Commit 207696b17f38 ("tpm: use a map for tpm2_calc_ordinal_duration()")
>> inadvertently reduced these command timeouts from 300 seconds to 30
>> seconds. Restore them to 300 seconds to avoid spurious failures.
>
> Please document such a platform.
Thanks for your comments, I will add the platform after the internal 
alignment.
>
>> Fixes: 207696b17f38 ("tpm: use a map for tpm2_calc_ordinal_duration()")
>>
>> Signed-off-by: Baoli.Zhang <baoli.zhang@linux.intel.com>
>
> It’d be great if you remove the dot from your name:
>
>     git config --global user.name "Baoli Zhang"
>
Yes,  will remove it in v2.
>> Co-developed-by: lili.li <lili.li@intel.com>
>
> Same here. Maybe spell it Lili Li?
>
>     git commit --amend --author="BaoliZhang 
> <baoli.zhang@linux.intel.com>" -s
>
Yes, her name is Lili Li. Will also remove  dot from her name.
>> ---
>>   drivers/char/tpm/tpm2-cmd.c | 6 +++---
>>   1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/char/tpm/tpm2-cmd.c b/drivers/char/tpm/tpm2-cmd.c
>> index 3a77be7ebf4aa..430022f695f24 100644
>> --- a/drivers/char/tpm/tpm2-cmd.c
>> +++ b/drivers/char/tpm/tpm2-cmd.c
>> @@ -71,9 +71,9 @@ static const struct {
>>       {TPM2_CC_HIERARCHY_CHANGE_AUTH, 2000},
>>       {TPM2_CC_GET_CAPABILITY, 750},
>>       {TPM2_CC_NV_READ, 2000},
>> -    {TPM2_CC_CREATE_PRIMARY, 30000},
>> -    {TPM2_CC_CREATE, 30000},
>> -    {TPM2_CC_CREATE_LOADED, 30000},
>> +    {TPM2_CC_CREATE_PRIMARY, 300000},
>> +    {TPM2_CC_CREATE, 300000},
>> +    {TPM2_CC_CREATE_LOADED, 300000},
>>   };
>>     /**
>
>

  reply	other threads:[~2026-04-13  1:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10  1:49 [PATCH v1] tpm: restore timeout for key creation commands Baoli.Zhang
2026-04-10  6:49 ` Paul Menzel
2026-04-13  1:31   ` Zhang, Baoli [this message]
2026-04-15  2:31 ` 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=90a02329-5e95-4eb8-ac47-028690bf52b3@linux.intel.com \
    --to=baoli.zhang@linux.intel.com \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=lili.li@intel.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=pmenzel@molgen.mpg.de \
    --cc=serge@hallyn.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