diff options
| author | Jonathan Neuschäfer <j.neuschaefer@gmx.net> | 2018-10-29 22:52:42 +0100 |
|---|---|---|
| committer | Philipp Deppenwiese <zaolin.daisuki@gmail.com> | 2018-10-30 12:12:50 +0000 |
| commit | 61322d7ad24ffcbd5b016da82c3fe2b804b611f7 (patch) | |
| tree | 005ec326f194dc54dadd98ade2a4733860ea9661 | |
| parent | dfbe6bd5c38d5feb6aa2778b2351cb13e0b1ecc8 (diff) | |
security/tpm: Fix references to tpm_setup function
Change-Id: Ia97ddcd5471f8e5db50f57b67a766f08a08180b1
Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
Reviewed-on: https://review.coreboot.org/29349
Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Reviewed-by: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
| -rw-r--r-- | src/security/tpm/tspi/tspi.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/security/tpm/tspi/tspi.c b/src/security/tpm/tspi/tspi.c index d9cade981d..0b6f9bcff2 100644 --- a/src/security/tpm/tspi/tspi.c +++ b/src/security/tpm/tspi/tspi.c @@ -103,10 +103,10 @@ static uint32_t tpm_setup_epilogue(uint32_t result) /* * tpm_setup starts the TPM and establishes the root of trust for the - * anti-rollback mechanism. SetupTPM can fail for three reasons. 1 A bug. 2 a - * TPM hardware failure. 3 An unexpected TPM state due to some attack. In + * anti-rollback mechanism. tpm_setup can fail for three reasons. 1 A bug. + * 2 a TPM hardware failure. 3 An unexpected TPM state due to some attack. In * general we cannot easily distinguish the kind of failure, so our strategy is - * to reboot in recovery mode in all cases. The recovery mode calls SetupTPM + * to reboot in recovery mode in all cases. The recovery mode calls tpm_setup * again, which executes (almost) the same sequence of operations. There is a * good chance that, if recovery mode was entered because of a TPM failure, the * failure will repeat itself. (In general this is impossible to guarantee |