From: Jarkko Sakkinen <jarkko@kernel.org>
To: Maurice Hieronymus <mhi@mailbox.org>
Cc: peterhuewe@gmx.de, linux-integrity@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: tpm2: Fix ill defined assertions
Date: Tue, 25 Nov 2025 17:36:06 +0200 [thread overview]
Message-ID: <aSXM5l47FCN81gan@kernel.org> (raw)
In-Reply-To: <20251123111809.24634-1-mhi@mailbox.org>
On Sun, Nov 23, 2025 at 12:18:09PM +0100, Maurice Hieronymus wrote:
> Remove parentheses around assert statements in Python. With parentheses,
> assert always evaluates to True, making the checks ineffective.
>
> Signed-off-by: Maurice Hieronymus <mhi@mailbox.org>
> ---
> tools/testing/selftests/tpm2/tpm2.py | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/tpm2/tpm2.py b/tools/testing/selftests/tpm2/tpm2.py
> index bba8cb54548e..3d130c30bc7c 100644
> --- a/tools/testing/selftests/tpm2/tpm2.py
> +++ b/tools/testing/selftests/tpm2/tpm2.py
> @@ -437,7 +437,7 @@ class Client:
>
> def extend_pcr(self, i, dig, bank_alg = TPM2_ALG_SHA1):
> ds = get_digest_size(bank_alg)
> - assert(ds == len(dig))
> + assert ds == len(dig)
>
> auth_cmd = AuthCommand()
>
> @@ -589,7 +589,7 @@ class Client:
> def seal(self, parent_key, data, auth_value, policy_dig,
> name_alg = TPM2_ALG_SHA1):
> ds = get_digest_size(name_alg)
> - assert(not policy_dig or ds == len(policy_dig))
> + assert not policy_dig or ds == len(policy_dig)
>
> attributes = 0
> if not policy_dig:
>
> base-commit: 821e6e2a328bb907d40f8d1141d8b6c079aa7340
> --
> 2.50.1
>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
BR, Jarkko
prev parent reply other threads:[~2025-11-25 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-23 11:18 [PATCH] selftests: tpm2: Fix ill defined assertions Maurice Hieronymus
2025-11-25 15:36 ` Jarkko Sakkinen [this message]
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=aSXM5l47FCN81gan@kernel.org \
--to=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mhi@mailbox.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