From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: David Howells <dhowells@redhat.com>, Petr Vorel <pvorel@suse.cz>,
shuah <shuah@kernel.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-integrity@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, Eric Biggers <ebiggers@kernel.org>
Subject: Re: [PATCH v1] selftest/trustedkeys: TPM 1.2 trusted keys test
Date: Mon, 28 Oct 2019 22:35:00 +0200 [thread overview]
Message-ID: <20191028203500.GB8279@linux.intel.com> (raw)
In-Reply-To: <1571945046.11756.5.camel@linux.ibm.com>
On Thu, Oct 24, 2019 at 03:24:06PM -0400, Mimi Zohar wrote:
> Hi Jarkko,
>
> Please note that I'm seeing "add_key: Timer expired" frequently. This
> is something new. I have no idea if this is a new TPM or keys
> regression.
Is it possible to bisect this? I cannot run the test script that you
made at the moment because of dependencies.
I'll try to work on image with BuildRoot that would have TrouSerS.
I recall it had recipe for it. So probably late this week or early
next week I'll be able to help finding the root cause.
/Jarkko
next prev parent reply other threads:[~2019-10-28 20:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 19:14 [PATCH v1] selftest/trustedkeys: TPM 1.2 trusted keys test Mimi Zohar
2019-10-24 19:24 ` Mimi Zohar
2019-10-28 20:35 ` Jarkko Sakkinen [this message]
2019-10-28 20:30 ` Jarkko Sakkinen
2019-10-28 20:40 ` Jarkko Sakkinen
2019-10-28 20:45 ` Mimi Zohar
2019-10-29 9:15 ` Jarkko Sakkinen
2019-10-29 9:25 ` Jarkko Sakkinen
2019-10-29 11:45 ` Jarkko Sakkinen
2019-10-29 11:49 ` 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=20191028203500.GB8279@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dhowells@redhat.com \
--cc=ebiggers@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pvorel@suse.cz \
--cc=shuah@kernel.org \
--cc=zohar@linux.ibm.com \
/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).