From: Jason Gunthorpe <jgg@ziepe.ca>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH] tpm: fix selftest failure regression
Date: Sun, 18 Feb 2018 10:08:31 -0700 [thread overview]
Message-ID: <20180218170831.GA4476@ziepe.ca> (raw)
In-Reply-To: <1518812108.4475.21.camel@HansenPartnership.com>
On Fri, Feb 16, 2018 at 12:15:08PM -0800, James Bottomley wrote:
> It isn't currently since it uses tpm_transmit directly. My thought on
> this is that if the TPM hasn't got its testing crap together by the
> time we enter userspace (which will be 10 or more seconds after we
> first sent the test commands), then we really have a problem and the
> user should see it.
Why would it be 10s? My embedded systems got to userspace in something
like 0.5s after sending the startup.
Not sure what to do here.. Our model has been that userspace gets a
raw view - but it has also been that the kernel makes the TPM fully
ready.
Jason
next prev parent reply other threads:[~2018-02-18 17:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1518122886.21828.20.camel@HansenPartnership.com>
2018-02-15 13:55 ` [PATCH] tpm: fix selftest failure regression Jarkko Sakkinen
2018-02-16 8:34 ` Jarkko Sakkinen
2018-02-16 18:17 ` James Bottomley
2018-02-16 18:59 ` James Bottomley
2018-02-16 19:26 ` Alexander Steffen
2018-02-16 19:45 ` James Bottomley
2018-02-20 14:24 ` Jarkko Sakkinen
2018-02-20 14:33 ` James Bottomley
2018-04-08 19:11 ` Ken Goldman
2018-02-20 13:30 ` Jarkko Sakkinen
2018-02-20 13:57 ` James Bottomley
2018-02-20 17:22 ` Jarkko Sakkinen
2018-02-20 17:27 ` James Bottomley
2018-02-16 20:15 ` James Bottomley
2018-02-18 17:08 ` Jason Gunthorpe [this message]
2018-02-18 17:16 ` James Bottomley
2018-02-18 17:36 ` Jason Gunthorpe
2018-02-18 18:06 ` James Bottomley
2018-02-20 14:25 ` 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=20180218170831.GA4476@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.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 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).