From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-security-module@vger.kernel.org,
tpmdd-devel@lists.sourceforge.net,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [tpmdd-devel] [PATCH RFC v3 5/5] tpm2: expose resource manager via a device link /dev/tpms<n>
Date: Sun, 22 Jan 2017 22:30:55 +0200 [thread overview]
Message-ID: <20170122203055.zg52yraahqvn4rbv@intel.com> (raw)
In-Reply-To: <1485110892.2504.12.camel@HansenPartnership.com>
On Sun, Jan 22, 2017 at 10:48:12AM -0800, James Bottomley wrote:
> On Sun, 2017-01-22 at 09:49 -0800, James Bottomley wrote:
> > On Fri, 2017-01-20 at 23:05 +0200, Jarkko Sakkinen wrote:
> > > 'tabrm4' branch has been now rebased. It's now on top of master
> > > branch that contains Stefan's latest patch (min body length check)
> > > that I've reviewed and tested. It also contains your updated
> > > /dev/tpms patch.
> > >
> > > I guess the 5 commits that are there now are such that we have
> > > fairly good consensus, don't we? If so, can I add your reviewed-by
> > > and tested-by to my commits and vice versa?
> >
> > We're still failing my test_transients. This is the full python of
> > the test case:
> >
> >
> > def test_transients(self):
> > k = self.open_transients()
> > self.c.flush_context(k[0])
> > self.c.change_auth(self.c.SRK, k[1], None, pwd1)
> > ...
> >
> > It's failing at self.c.flush_context(k[0]) with TPM_RC_VALUE. It's
> > the same problem Ken complained about: TPM2_FlushContext doesn't have
> > a declared handle area so we don't translate the handle being sent
> > down. We have to fix this either by intercepting the flush and
> > manually translating the context, or by being dangerously clever and
> > marking flush as a command which takes one handle.
>
> This is what the dangerously clever fix looks like. With this and a
> few other changes, my smoke tests now pass.
>
> James
I don't want to be clever here. I will rather intercept the body and
try to keep the core code simple and easy to understand.
/Jarkko
next prev parent reply other threads:[~2017-01-22 20:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 13:12 [PATCH RFC v3 0/5] RFC: in-kernel resource manager Jarkko Sakkinen
2017-01-16 13:12 ` [PATCH RFC v3 1/5] tpm: validate TPM 2.0 commands Jarkko Sakkinen
2017-01-16 13:12 ` [PATCH RFC v3 2/5] tpm: export tpm2_flush_context_cmd Jarkko Sakkinen
2017-01-16 13:12 ` [PATCH RFC v3 3/5] tpm: infrastructure for TPM spaces Jarkko Sakkinen
2017-01-16 13:12 ` [PATCH RFC v3 4/5] tpm: split out tpm-dev.c into tpm-dev.c and tpm-common-dev.c Jarkko Sakkinen
2017-01-16 13:12 ` [PATCH RFC v3 5/5] tpm2: expose resource manager via a device link /dev/tpms<n> Jarkko Sakkinen
2017-01-16 16:14 ` Jason Gunthorpe
2017-01-16 17:24 ` Jarkko Sakkinen
2017-01-16 17:28 ` [tpmdd-devel] " James Bottomley
2017-01-17 7:14 ` Jarkko Sakkinen
2017-01-18 15:01 ` James Bottomley
2017-01-19 10:49 ` Jarkko Sakkinen
2017-01-19 12:19 ` James Bottomley
2017-01-20 13:39 ` Jarkko Sakkinen
2017-01-20 21:05 ` Jarkko Sakkinen
2017-01-21 19:28 ` James Bottomley
2017-01-22 14:49 ` Jarkko Sakkinen
2017-01-21 20:38 ` James Bottomley
2017-01-22 14:49 ` Jarkko Sakkinen
2017-01-22 17:49 ` James Bottomley
2017-01-22 18:48 ` James Bottomley
2017-01-22 20:30 ` Jarkko Sakkinen [this message]
2017-01-22 21:01 ` Jarkko Sakkinen
2017-01-22 21:04 ` Jarkko Sakkinen
2017-01-22 21:36 ` James Bottomley
2017-01-23 14:09 ` Jarkko Sakkinen
2017-01-23 16:14 ` James Bottomley
2017-01-24 12:03 ` Jarkko Sakkinen
2017-01-23 16:58 ` Jarkko Sakkinen
2017-01-23 21:42 ` Jarkko Sakkinen
2017-01-23 22:16 ` James Bottomley
2017-01-25 13:40 ` Jarkko Sakkinen
2017-01-25 13:42 ` Jarkko Sakkinen
2017-01-27 0:29 ` James Bottomley
2017-01-27 6:45 ` Jarkko Sakkinen
2017-01-25 20:23 ` Jarkko Sakkinen
2017-01-22 20:24 ` Jarkko Sakkinen
2017-01-19 10:42 ` 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=20170122203055.zg52yraahqvn4rbv@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
/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).