linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Laurent Bigonville <bigon@debian.org>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
	linux-integrity@vger.kernel.org
Subject: Re: TPM returned invalid status
Date: Fri, 12 Feb 2021 12:46:24 +0200	[thread overview]
Message-ID: <YCZcgF6ofubvKsFB@kernel.org> (raw)
In-Reply-To: <22b860c1-c494-7a4d-73f3-7c9e90ab1ae8@debian.org>

On Mon, Feb 08, 2021 at 03:47:57PM +0100, Laurent Bigonville wrote:
> Le 8/02/21 à 04:33, James Bottomley a écrit :
> > On Sat, 2021-02-06 at 00:31 +0100, Laurent Bigonville wrote:
> > > Hello,
> > > 
> > > I already posted that beginning of January in reply to "tpm_tis:
> > > Clean
> > > up locality release", but I didn't really got a reply
> > > 
> > > With debian unstable (Linux fornost 5.10.0-3-amd64 #1 SMP Debian
> > > 5.10.12-1 (2021-01-30) x86_64 GNU/Linux), I get the following error:
> > Sorry, forgot to cc you.  We're iterating to this as the fix:
> > 
> > https://lore.kernel.org/linux-integrity/20201001180925.13808-5-James.Bottomley@HansenPartnership.com/
> > 
> > If you want to test it out.
> 
> I recompiled 5.11.0-rc7+ with the patch and I still get the same trace

Yeah, still pending the fix for probe.

The whole thread is here:

https://lore.kernel.org/linux-integrity/20210123014247.989368-1-lma@semihalf.com/

/Jarkko

  reply	other threads:[~2021-02-12 10:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05 23:31 TPM returned invalid status Laurent Bigonville
2021-02-08  3:33 ` James Bottomley
2021-02-08 14:47   ` Laurent Bigonville
2021-02-12 10:46     ` Jarkko Sakkinen [this message]
2021-02-12 10:44   ` Jarkko Sakkinen
2021-02-13 18:32     ` James Bottomley
2021-02-16  7:33       ` Jarkko Sakkinen
2021-02-16  8:19         ` 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=YCZcgF6ofubvKsFB@kernel.org \
    --to=jarkko@kernel.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=bigon@debian.org \
    --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).