All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Johannes Holland <johannes.holland@infineon.com>
Cc: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	peterhuewe@gmx.de, jgg@ziepe.ca
Subject: Re: [PATCH] tpm: increase timeout for kselftests
Date: Wed, 11 May 2022 18:14:08 +0300	[thread overview]
Message-ID: <YnvSwJxOg+IZxrxz@kernel.org> (raw)
In-Reply-To: <20220510111607.22984-1-johannes.holland@infineon.com>

On Tue, May 10, 2022 at 01:16:08PM +0200, Johannes Holland wrote:
> Due to CreatePrimary commands which need to create RSA keys of
> increasing size, the timeout value need to be raised, as well.
> Default is 300s.
> 
> Signed-off-by: Johannes Holland <johannes.holland@infineon.com>
> ---
> A timeout of anything below 600s still lead to occasional timeouts for
> me. Therefore, I propose 600s as a new value. 
> 
>  tools/testing/selftests/tpm2/settings | 2 ++
>  1 file changed, 2 insertions(+)
>  create mode 100644 tools/testing/selftests/tpm2/settings
> 
> diff --git a/tools/testing/selftests/tpm2/settings b/tools/testing/selftests/tpm2/settings
> new file mode 100644
> index 000000000000..919bc3803f03
> --- /dev/null
> +++ b/tools/testing/selftests/tpm2/settings
> @@ -0,0 +1,2 @@
> +timeout=600
> +
> -- 
> 2.34.1
> 

Could cope but I did not get why it needs to be raised.

BR, Jarkko

  parent reply	other threads:[~2022-05-11 15:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 11:16 [PATCH] tpm: increase timeout for kselftests Johannes Holland
2022-05-10 11:56 ` Paul Menzel
2022-05-11 15:14 ` Jarkko Sakkinen [this message]
2022-05-20 13:28   ` Stefan Mahnke-Hartmann
2022-05-23 19:59     ` Jarkko Sakkinen
2022-06-20 14:45       ` Stefan Mahnke-Hartmann
2022-06-26  6:18         ` 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=YnvSwJxOg+IZxrxz@kernel.org \
    --to=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=johannes.holland@infineon.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.