From: Jarkko Sakkinen <jarkko@kernel.org>
To: Stefan Berger <stefanb@linux.ibm.com>
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org, peterhuewe@gmx.de,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
skhan@linuxfoundation.org
Subject: Re: [PATCH v3 1/3] selftests: tpm2: Probe for available PCR bank
Date: Tue, 30 Nov 2021 01:37:20 +0200 [thread overview]
Message-ID: <YaVkMF8aKuef4K48@iki.fi> (raw)
In-Reply-To: <2557c1e2-b0fa-8729-0eb0-6ae68ee6f653@linux.ibm.com>
On Fri, Nov 26, 2021 at 10:43:42PM -0500, Stefan Berger wrote:
>
> On 11/26/21 19:29, Jarkko Sakkinen wrote:
> > On Wed, 2021-11-24 at 19:38 -0500, Stefan Berger wrote:
> > > From: Stefan Berger <stefanb@linux.ibm.com>
> > >
> > > Probe for an available PCR bank to accommodate devices that do not have a
> > What does "probing for an vailable PCR bank" even mean?
>
> Checking ? Testing ? What's the difference to those words?
This would an exact description:
"Some devices do not have SHA1 bank available. Try to use SHA256 as a
fallback when this occurs."
It does not leave any open territory what the patch does. It does exactly
this, not more or less.
/Jarkko
next prev parent reply other threads:[~2021-11-29 23:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 0:38 [PATCH v3 0/3] selftests: tpm2: Probe for available PCR bank Stefan Berger
2021-11-25 0:38 ` [PATCH v3 1/3] " Stefan Berger
2021-11-27 0:29 ` Jarkko Sakkinen
2021-11-27 3:43 ` Stefan Berger
2021-11-29 23:37 ` Jarkko Sakkinen [this message]
2021-11-25 0:38 ` [PATCH v3 2/3] selftests: tpm2: Reset the dictionary attack lock Stefan Berger
2021-11-25 0:38 ` [PATCH v3 3/3] selftests: tpm2: Add support for SHA-384 and SHA-512 Stefan Berger
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=YaVkMF8aKuef4K48@iki.fi \
--to=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=skhan@linuxfoundation.org \
--cc=stefanb@linux.ibm.com \
--cc=stefanb@linux.vnet.ibm.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 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.