public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Alexander.Steffen@infineon.com
Cc: pmenzel@molgen.mpg.de, linux-integrity@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Regression 4.15-rc2] New messages `tpm tpm0: A TPM error (2314) occurred continue selftest`
Date: Thu, 7 Dec 2017 11:37:43 -0700	[thread overview]
Message-ID: <20171207183743.GB16884@ziepe.ca> (raw)
In-Reply-To: <32b0e6c1292f4818825e9e0e9bff4d39@infineon.com>

On Thu, Dec 07, 2017 at 03:56:07PM +0000, Alexander.Steffen@infineon.com wrote:

> > If these are intentional, it'd be great
> > to give some hint to the user, what effect this has.
> 
> I agree that those error messages in their current form are not that
> helpful for the users. But they are part of the general driver
> architecture, and are also caused by other parts of the code
> (e.g. when using a TPM 1.2 that is deactivated or when the platform
> did not send a startup command). We should find a way to hide (or at
> least mark) those kind of expected errors.

Other parts of the TPM code did supresses 'expected' errors like this,
I'm not sure if it got removed during Jarkko's cleanup though - we
need to put stuff like that back, it should not printk for something
like this.

For this, if we are waiting then it should compute an absolute time
after which it will give up.

Code it like this instead and get rid of the ugly 'duration' scheme.

ktime_t stop = ktime_add_ns(ktime_get(), [timeout in ns]);
do
{
}
while (ktime_before(ktime_get(), stop);

Jason

  reply	other threads:[~2017-12-07 18:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-06 12:34 [Regression 4.15-rc2] New messages `tpm tpm0: A TPM error (2314) occurred continue selftest` Paul Menzel
2017-12-06 16:40 ` Jason Gunthorpe
2017-12-07 15:56 ` Alexander.Steffen
2017-12-07 18:37   ` Jason Gunthorpe [this message]
2017-12-08 12:14     ` Alexander.Steffen
2017-12-08 15:56       ` Jason Gunthorpe
2017-12-08 16:07         ` Paul Menzel
2017-12-08 16:18           ` Jason Gunthorpe
2017-12-11 12:54             ` Paul Menzel
2017-12-11 16:08               ` Alexander.Steffen
2017-12-14 10:33                 ` Paul Menzel
2017-12-14 12:20                   ` Alexander.Steffen
2017-12-14 14:15                     ` Mario.Limonciello
2017-12-14 16:12                       ` Alexander.Steffen
2017-12-14 19:43                         ` Mario.Limonciello
2017-12-15 11:54                           ` Paul Menzel
2017-12-15 14:39                             ` Mario.Limonciello
2017-12-15 15:10                               ` Paul Menzel
2017-12-15 15:24                                 ` Mario.Limonciello
2017-12-15 15:38                                   ` Paul Menzel
2017-12-15 14:54                             ` Alexander.Steffen
2017-12-15 15:26                               ` Paul Menzel
2017-12-21 13:36               ` Mimi Zohar
2017-12-22 14:00                 ` Alexander.Steffen
2017-12-22 14:08                   ` Paul Menzel
2017-12-08 16:17         ` Mimi Zohar

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=20171207183743.GB16884@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=Alexander.Steffen@infineon.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.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