From: Jarkko Sakkinen <jarkko@kernel.org>
To: Jacqueline Wong <jacqwong@google.com>
Cc: linux-integrity@vger.kernel.org, peterhuewe@gmx.de, jgg@ziepe.ca,
axelrasmussen@google.com
Subject: Re: [PATCH v2 0/2] tpm_tis: fix retry exhaustion and add logging
Date: Wed, 15 Apr 2026 05:40:17 +0300 [thread overview]
Message-ID: <ad76kaEBsVIjeOX-@kernel.org> (raw)
In-Reply-To: <20260411003300.1823020-1-jacqwong@google.com>
On Sat, Apr 11, 2026 at 12:32:58AM +0000, Jacqueline Wong wrote:
> The Fix:
> - Patch 1: Adds error logs to identify the specific hardware status mismatch.
> - Patch 2: Stops execution immediately when retries are exhausted.
>
> v2 changes:
> - Split logging and logic into separate patches.
> - Added retry count to the error message.
> - Included dmesg traces below.
>
> Testing:
> Dmesg traces obtained using error injection to simulate status register mismatches.
>
> Before:
> [ 130.288751] tpm tpm0: Operation Timed out
> [ 250.306070] tpm tpm0: Operation Timed out
> [ 250.310173] tpm tpm0: A TPM error (-62) occurred attempting to determine the timeouts
>
> After:
> [ 10.271547] tpm tpm0: TPM_STS_DATA_EXPECT should be unset. sts = 0x00000080
> ...
> [ 10.646283] tpm tpm0: TPM_STS_DATA_EXPECT should be unset. sts = 0x00000080
> [ 10.653461] tpm tpm0: Exhausted 50 tpm_tis_send_data retries
> [ 10.659304] tpm tpm0: tpm_try_transmit: send(): error -5
> [ 10.665435] tpm tpm0: TPM_STS_DATA_EXPECT should be unset. sts = 0x00000080
> ...
> [ 11.037198] tpm tpm0: TPM_STS_DATA_EXPECT should be unset. sts = 0x00000080
> [ 11.044441] tpm tpm0: Exhausted 50 tpm_tis_send_data retries
> [ 11.050288] tpm tpm0: tpm_try_transmit: send(): error -5
> [ 11.055723] tpm tpm0: A TPM error (-5) occurred attempting to determine the timeouts
>
> Jacqueline Wong (2):
> tpm: tpm_tis: add error logging for data transfer
> tpm: tpm_tis: stop transmit if retries are exhausted
>
> drivers/char/tpm/tpm_tis_core.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> --
> 2.53.0.1213.gd9a14994de-goog
>
OK, I dropped the patch that as I applied as I did not see this :-)
Now that we are cycling, please send v3 with checkpatch --strict passing
BR, Jarkko
prev parent reply other threads:[~2026-04-15 2:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-11 0:32 [PATCH v2 0/2] tpm_tis: fix retry exhaustion and add logging Jacqueline Wong
2026-04-11 0:32 ` [PATCH v2 1/2] tpm: tpm_tis: add error logging for data transfer Jacqueline Wong
2026-04-11 0:33 ` [PATCH v2 2/2] tpm: tpm_tis: stop transmit if retries are exhausted Jacqueline Wong
2026-04-15 2:40 ` 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=ad76kaEBsVIjeOX-@kernel.org \
--to=jarkko@kernel.org \
--cc=axelrasmussen@google.com \
--cc=jacqwong@google.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@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.