From: Jerry Snitselaar <jsnitsel@redhat.com>
To: linux-integrity@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Peter Huewe <peterhuewe@gmx.de>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>
Subject: [PATCH 0/2 v2] tpm: add update_durations class op to allow override of chip supplied values
Date: Tue, 27 Aug 2019 17:46:19 -0700 [thread overview]
Message-ID: <20190828004621.29050-1-jsnitsel@redhat.com> (raw)
We've run into a case where a customer has an STM TPM 1.2 chip
(version 1.2.8.28) that is getting into an inconsistent state and
they end up getting tpm transmit errors. In really old tpm code this
wasn't seen because the code that grabbed the duration values from the
chip could fail silently, and would proceed to just use default values
and move forward. More recent code though successfully gets the
duration values from the chip, and using those values this particular
chip version gets into the state seen by the customer.
The idea with this patchset is to provide a facility like the
update_timeouts operation to allow the override of chip supplied
values.
I went back and looked at the original submission thread, and updated
Alexey's patches based on Jarkko's suggestions for v2.
next reply other threads:[~2019-08-28 0:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 0:46 Jerry Snitselaar [this message]
2019-08-28 0:46 ` [PATCH 1/2 v2] tpm: provide a way to override the chip returned durations Jerry Snitselaar
2019-08-29 13:27 ` Jarkko Sakkinen
2019-08-28 0:46 ` [PATCH 2/2 v2] tpm_tis: override durations for STM tpm with firmware 1.2.8.28 Jerry Snitselaar
2019-08-29 14:40 ` Jarkko Sakkinen
2019-08-29 14:41 ` Jarkko Sakkinen
2019-08-29 18:04 ` Jerry Snitselaar
2019-08-29 20:25 ` Jerry Snitselaar
2019-08-29 22:23 ` 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=20190828004621.29050-1-jsnitsel@redhat.com \
--to=jsnitsel@redhat.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).