From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-integrity@vger.kernel.org
Subject: Re: [PATCH v3] tpm: fix intermittent failure with self tests
Date: Wed, 21 Feb 2018 09:25:18 +0200 [thread overview]
Message-ID: <20180221072518.emmos62oegedw7rz@linux.intel.com> (raw)
In-Reply-To: <1519168191.4446.31.camel@HansenPartnership.com>
On Tue, Feb 20, 2018 at 06:09:51PM -0500, James Bottomley wrote:
> On Tue, 2018-02-20 at 23:28 +0200, Jarkko Sakkinen wrote:
> > On Tue, Feb 20, 2018 at 11:27:25PM +0200, Jarkko Sakkinen wrote:
> > >
> > > On Tue, Feb 20, 2018 at 09:26:00PM +0200, Jarkko Sakkinen wrote:
> > > >
> > > > On Tue, Feb 20, 2018 at 12:51:51PM -0500, James Bottomley wrote:
> > > > >
> > > > > On Tue, 2018-02-20 at 19:43 +0200, Jarkko Sakkinen wrote:
> > > > > >
> > > > > > I get merge conflicts in my tree but I'll review this.
> > > > >
> > > > > You told me to rebase it on that patch that wasn't in your
> > > > > tree:
> > > > >
> > > > > https://patchwork.kernel.org/patch/10208965/
> > > > >
> > > > > If you put it in your tree, I can just rebase on top of
> > > > > everything.
> > > > >
> > > > > James
> > > >
> > > > Aah. Sorry, my bad I'll move forward on testing :-)
> > > >
> > > > /Jarkko
> > >
> > > Tested-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
> > >
> > > /Jarkko
> >
> > These must be taken away:
> >
> > [ 2.843641] tpm tpm0: TPM: running incremental selftest
> > [ 2.854087] tpm tpm0: TPM: selftest succeeded
>
> I'm not wedded to having the messages, but it helps give context when
> something like this happens:
>
> [ 1.550099] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 2)
> [ 1.550108] tpm tpm0: TPM: running incremental selftest
> [ 1.602294] tpm tpm0: A TPM error (323) occurred incremental selftest
> [ 1.602320] tpm tpm0: TPM: incremental selftest failed
> [ 1.602322] tpm tpm0: TPM: running full selftest
> [ 2.523689] tpm tpm0: TPM: selftest succeeded
>
> It also helps explain why I lost a second in the boot sequence to the
> TPM having to run a full self test.
>
> Without the chatty messages, what you see is
>
> [ 1.550099] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 2)
> [
> 1.602294] tpm tpm0: A TPM error (323) occurred incremental selftest
>
> Which is a bit harder to interpret.
>
> James
Way too much bloat to klog. Telling whether the full or incremental test
failed makes sense. Otherwise, not so much.
I updated the patch (v4) with things cleaned up that add bloat to the
driver code and squashed tpm_buf patch to it.
/Jarkko
next prev parent reply other threads:[~2018-02-21 7:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 12:24 [PATCH v3] tpm: fix intermittent failure with self tests James Bottomley
2018-02-20 17:43 ` Jarkko Sakkinen
2018-02-20 17:51 ` James Bottomley
2018-02-20 19:26 ` Jarkko Sakkinen
2018-02-20 21:27 ` Jarkko Sakkinen
2018-02-20 21:28 ` Jarkko Sakkinen
2018-02-20 21:29 ` Jarkko Sakkinen
2018-02-20 23:09 ` James Bottomley
2018-02-21 7:25 ` Jarkko Sakkinen [this message]
2018-02-21 7:42 ` Paul Menzel
2018-02-21 13:36 ` Jarkko Sakkinen
2018-02-21 7:04 ` Paul Menzel
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=20180221072518.emmos62oegedw7rz@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=James.Bottomley@HansenPartnership.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