mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan McDowell <noodles@earth.li>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Stefan Berger <stefanb@linux.ibm.com>,
	linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tpm, tpm_tis: Workaround failed command reception on Infineon devices
Date: Fri, 21 Mar 2025 16:49:15 +0000	[thread overview]
Message-ID: <Z92YiwubEvzsm1SO@earth.li> (raw)
In-Reply-To: <Z87Y69l5_GbzlLfp@earth.li>

Jarkko, I've realised I've somehow introduced a typo in the patch below 
that means it doesn't fire correctly; I'm not sure how this happened as 
my local copy I was testing on is definitely correct. Would you like a 
one line fix up patch, or can you manually fix it up in your tree?

This hunk:

>@@ -545,9 +551,11 @@ static int tpm_tis_send_main(struct tpm_chip *chip, const u8 *buf, size_t len)
> 		if (rc >= 0)
> 			/* Data transfer done successfully */
> 			break;
>-		else if (rc != -EIO)
>+		else if (rc != EAGAIN && rc != -EIO)
> 			/* Data transfer failed, not recoverable */
> 			return rc;
>+
>+		usleep_range(priv->timeout_min, priv->timeout_max);
> 	}
> 	/* go and do it */

should be "rc != -EAGAIN" - the "-" sign has somehow been lost.

Apologies for this, let me know what's easiest for you in terms of 
resolving it.

On Mon, Mar 10, 2025 at 12:19:55PM +0000, Jonathan McDowell wrote:
>From: Jonathan McDowell <noodles@meta.com>
>
>Some Infineon devices have a issue where the status register will get
>stuck with a quick REQUEST_USE / COMMAND_READY sequence. This is not
>simply a matter of requiring a longer timeout; the work around is to
>retry the command submission. Add appropriate logic to do this in the
>send path.
>
>This is fixed in later firmware revisions, but those are not always
>available, and cannot generally be easily updated from outside a
>firmware environment.
>
>Testing has been performed with a simple repeated loop of doing a
>TPM2_CC_GET_CAPABILITY for TPM_CAP_PROP_MANUFACTURER using the Go code
>at:
>
> https://the.earth.li/~noodles/tpm-stuff/timeout-reproducer-simple.go
>
>It can take several hours to reproduce, and several million operations.
>
>Signed-off-by: Jonathan McDowell <noodles@meta.com>
>---
>v2: Rename flag to TPM_TIS_STATUS_VALID_RETRY
>
> drivers/char/tpm/tpm_tis_core.c | 17 ++++++++++++++---
> drivers/char/tpm/tpm_tis_core.h |  1 +
> include/linux/tpm.h             |  1 +
> 3 files changed, 16 insertions(+), 3 deletions(-)
>
>diff --git a/drivers/char/tpm/tpm_tis_core.c b/drivers/char/tpm/tpm_tis_core.c
>index c969a1793184..4ab69c3e103c 100644
>--- a/drivers/char/tpm/tpm_tis_core.c
>+++ b/drivers/char/tpm/tpm_tis_core.c
>@@ -463,7 +463,10 @@ static int tpm_tis_send_data(struct tpm_chip *chip, const u8 *buf, size_t len)
> 		if (wait_for_tpm_stat(chip, TPM_STS_VALID, chip->timeout_c,
> 					&priv->int_queue, false) < 0) {
>-			rc = -ETIME;
>+			if (test_bit(TPM_TIS_STATUS_VALID_RETRY, &priv->flags))
>+				rc = -EAGAIN;
>+			else
>+				rc = -ETIME;
> 			goto out_err;
> 		}
> 		status = tpm_tis_status(chip);
>@@ -480,7 +483,10 @@ static int tpm_tis_send_data(struct tpm_chip *chip, const u8 *buf, size_t len)
> 	if (wait_for_tpm_stat(chip, TPM_STS_VALID, chip->timeout_c,
> 				&priv->int_queue, false) < 0) {
>-		rc = -ETIME;
>+		if (test_bit(TPM_TIS_STATUS_VALID_RETRY, &priv->flags))
>+			rc = -EAGAIN;
>+		else
>+			rc = -ETIME;
> 		goto out_err;
> 	}
> 	status = tpm_tis_status(chip);
>@@ -545,9 +551,11 @@ static int tpm_tis_send_main(struct tpm_chip *chip, const u8 *buf, size_t len)
> 		if (rc >= 0)
> 			/* Data transfer done successfully */
> 			break;
>-		else if (rc != -EIO)
>+		else if (rc != EAGAIN && rc != -EIO)
> 			/* Data transfer failed, not recoverable */
> 			return rc;
>+
>+		usleep_range(priv->timeout_min, priv->timeout_max);
> 	}
> 	/* go and do it */
>@@ -1143,6 +1151,9 @@ int tpm_tis_core_init(struct device *dev, struct tpm_tis_data *priv, int irq,
> 		priv->timeout_max = TIS_TIMEOUT_MAX_ATML;
> 	}
>+	if (priv->manufacturer_id == TPM_VID_IFX)
>+		set_bit(TPM_TIS_STATUS_VALID_RETRY, &priv->flags);
>+
> 	if (is_bsw()) {
> 		priv->ilb_base_addr = ioremap(INTEL_LEGACY_BLK_BASE_ADDR,
> 					ILB_REMAP_SIZE);
>diff --git a/drivers/char/tpm/tpm_tis_core.h b/drivers/char/tpm/tpm_tis_core.h
>index 690ad8e9b731..970d02c337c7 100644
>--- a/drivers/char/tpm/tpm_tis_core.h
>+++ b/drivers/char/tpm/tpm_tis_core.h
>@@ -89,6 +89,7 @@ enum tpm_tis_flags {
> 	TPM_TIS_INVALID_STATUS		= 1,
> 	TPM_TIS_DEFAULT_CANCELLATION	= 2,
> 	TPM_TIS_IRQ_TESTED		= 3,
>+	TPM_TIS_STATUS_VALID_RETRY	= 4,
> };
> struct tpm_tis_data {
>diff --git a/include/linux/tpm.h b/include/linux/tpm.h
>index 20a40ade8030..6c3125300c00 100644
>--- a/include/linux/tpm.h
>+++ b/include/linux/tpm.h
>@@ -335,6 +335,7 @@ enum tpm2_cc_attrs {
> #define TPM_VID_WINBOND  0x1050
> #define TPM_VID_STM      0x104A
> #define TPM_VID_ATML     0x1114
>+#define TPM_VID_IFX      0x15D1
> enum tpm_chip_flags {
> 	TPM_CHIP_FLAG_BOOTSTRAPPED		= BIT(0),
>-- 
>2.48.1
>
>

J.

-- 
101 things you can't have too much of : 7 - Memory.

  parent reply	other threads:[~2025-03-21 16:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06  9:00 [PATCH] " Jonathan McDowell
2025-03-06 22:23 ` Jarkko Sakkinen
2025-03-07 16:36   ` Jonathan McDowell
2025-03-07 16:45     ` Jarkko Sakkinen
2025-03-10 12:19       ` [PATCH v2] " Jonathan McDowell
2025-03-10 14:12         ` Paul Menzel
2025-03-11  9:46         ` Jarkko Sakkinen
2025-03-21 16:49         ` Jonathan McDowell [this message]
2025-03-22 21:10           ` 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=Z92YiwubEvzsm1SO@earth.li \
    --to=noodles@earth.li \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=stefanb@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®