All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eddie James <eajames@linux.ibm.com>
To: openbmc@lists.ozlabs.org
Subject: [PATCH linux dev-5.15 3/7] tpm: tpm_tis: Verify TPM_STS register is valid after locality request
Date: Wed,  8 Dec 2021 13:17:54 -0600	[thread overview]
Message-ID: <20211208191758.20517-4-eajames@linux.ibm.com> (raw)
In-Reply-To: <20211208191758.20517-1-eajames@linux.ibm.com>

From: Amir Mizinski <amirmizi6@gmail.com>

An invalid TPM_STS value could be used when the following two events occur:
TPM does not update TPM_STS register after a locality request (TPM_STS
Initial value = 0xFF), and a TPM_STS register read occurs in the
tpm_tis_status(chip) function call.

In probe_itpm(), a call to tpm_tis_send_data() function is made after a
request_locality() call, and the condition
("if ((status & TPM_STS_COMMAND_READY) == 0)") is checked. At this moment
if the status value is 0xFF, then it is considered, wrongly, in “ready”
state (by checking only one bit). However, at this moment the TPM is, in
fact, in "Idle" state and remains in "Idle" state because
"tpm_tis_ready(chip);" was not executed.
Waiting for the condition TPM_STS.tpmGo == 0, will ensure that the TPM
status register has the correct value.

Suggested-by: Benoit Houyere <benoit.houyere@st.com>
Signed-off-by: Amir Mizinski <amirmizi6@gmail.com>
---
 drivers/char/tpm/tpm_tis_core.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/drivers/char/tpm/tpm_tis_core.c b/drivers/char/tpm/tpm_tis_core.c
index 7d6d07625600..9a38cbaef1c0 100644
--- a/drivers/char/tpm/tpm_tis_core.c
+++ b/drivers/char/tpm/tpm_tis_core.c
@@ -178,8 +178,12 @@ static int request_locality(struct tpm_chip *chip, int l)
 	} else {
 		/* wait for burstcount */
 		do {
-			if (check_locality(chip, l))
+			if (check_locality(chip, l)) {
+				if (tpm_tis_wait_for_stat(chip, TPM_STS_GO, 0, chip->timeout_c,
+							  &priv->int_queue, false) < 0)
+					return -ETIME;
 				return l;
+			}
 			tpm_msleep(TPM_TIMEOUT);
 		} while (time_before(jiffies, stop));
 	}
-- 
2.27.0


  parent reply	other threads:[~2021-12-08 19:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 19:17 [PATCH linux dev-5.15 0/7] Add tpm i2c ptp driver Eddie James
2021-12-08 19:17 ` [PATCH linux dev-5.15 1/7] tpm_tis: Fix expected bit handling Eddie James
2021-12-08 19:17 ` [PATCH linux dev-5.15 2/7] tpm: tpm_tis: Rewrite "tpm_tis_req_canceled()" Eddie James
2021-12-08 19:17 ` Eddie James [this message]
2021-12-08 19:17 ` [PATCH linux dev-5.15 4/7] tpm: tpm_tis: Add tpm_tis_i2c driver Eddie James
2021-12-08 19:17 ` [PATCH linux dev-5.15 5/7] tpm: Add YAML schema for TPM TIS I2C options Eddie James
2021-12-08 19:17 ` [PATCH linux dev-5.15 6/7] ARM: dts: aspeed: Rainier: Add TPM device Eddie James
2021-12-08 19:17 ` [PATCH linux dev-5.15 7/7] ARM: dts: aspeed: Everest: " Eddie James

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=20211208191758.20517-4-eajames@linux.ibm.com \
    --to=eajames@linux.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    /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.