From: Jarkko Sakkinen <jarkko@kernel.org>
To: linux-integrity@vger.kernel.org
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
David Howells <dhowells@redhat.com>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
linux-kernel@vger.kernel.org (open list),
keyrings@vger.kernel.org (open list:KEYS/KEYRINGS),
linux-security-module@vger.kernel.org (open list:SECURITY
SUBSYSTEM)
Subject: [PATCH v4 8/8] tpm: In tpm_get_random() replace 'retries' with a zero check
Date: Wed, 10 Dec 2025 19:20:26 +0200 [thread overview]
Message-ID: <20251210172027.109938-9-jarkko@kernel.org> (raw)
In-Reply-To: <20251210172027.109938-1-jarkko@kernel.org>
Check for zero byte read instead of having retries counter in order to make
wait flag properly enforcing. Progress is still guaranteed given the zero
check and iterations are capped up to TPM_MAX_RNG_DATA iterations at most
(as per theoretical limit).
Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
---
drivers/char/tpm/tpm-interface.c | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/char/tpm/tpm-interface.c b/drivers/char/tpm/tpm-interface.c
index 5cc2bbabd57a..594ad095a90b 100644
--- a/drivers/char/tpm/tpm-interface.c
+++ b/drivers/char/tpm/tpm-interface.c
@@ -620,7 +620,6 @@ int tpm_get_random(struct tpm_chip *chip, u8 *out, size_t max, bool wait)
{
u32 num_bytes = max;
u8 *out_ptr = out;
- int retries = 5;
int total = 0;
int rc;
@@ -646,8 +645,12 @@ int tpm_get_random(struct tpm_chip *chip, u8 *out, size_t max, bool wait)
else
rc = tpm1_get_random(chip, out_ptr, num_bytes);
- if (rc < 0)
+ if (rc <= 0) {
+ if (!rc)
+ rc = -EIO;
+
goto err;
+ }
if (!wait) {
total = rc;
@@ -657,7 +660,7 @@ int tpm_get_random(struct tpm_chip *chip, u8 *out, size_t max, bool wait)
out_ptr += rc;
total += rc;
num_bytes -= rc;
- } while (retries-- && total < max);
+ } while (total < max);
tpm_put_ops(chip);
return total ? total : -EIO;
--
2.39.5
prev parent reply other threads:[~2025-12-10 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 17:20 [PATCH v4 0/8] Streamline TPM2 HMAC sessions Jarkko Sakkinen
2025-12-10 17:20 ` [PATCH v4 1/8] KEYS: trusted: Remove dead branch from tpm2_unseal_cmd Jarkko Sakkinen
2025-12-10 17:20 ` [PATCH v4 2/8] tpm2-sessions: Define TPM2_NAME_MAX_SIZE Jarkko Sakkinen
2025-12-10 17:20 ` [PATCH v4 3/8] KEYS: trusted: Re-orchestrate tpm2_read_public() calls Jarkko Sakkinen
2025-12-10 17:20 ` [PATCH v4 4/8] tpm2-sessions: Remove AUTH_MAX_NAMES Jarkko Sakkinen
2025-12-10 17:20 ` [PATCH v4 5/8] tpm-buf: Remove tpm_buf_append_handle Jarkko Sakkinen
2025-12-10 17:20 ` [PATCH v4 6/8] tpm: Orchestrate TPM commands in tpm_get_random() Jarkko Sakkinen
2025-12-10 17:20 ` [PATCH v4 7/8] tpm: Send only one at most TPM2_GetRandom command Jarkko Sakkinen
2025-12-10 17:20 ` 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=20251210172027.109938-9-jarkko@kernel.org \
--to=jarkko@kernel.org \
--cc=dhowells@redhat.com \
--cc=jgg@ziepe.ca \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=peterhuewe@gmx.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