[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1484828380.3140.11.camel@HansenPartnership.com>
Date: Thu, 19 Jan 2017 07:19:40 -0500
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
Cc: tpmdd-devel@...ts.sourceforge.net,
open list <linux-kernel@...r.kernel.org>,
linux-security-module@...r.kernel.org
Subject: Re: [tpmdd-devel] [PATCH RFC v3 5/5] tpm2: expose resource manager
via a device link /dev/tpms<n>
On Thu, 2017-01-19 at 12:49 +0200, Jarkko Sakkinen wrote:
> On Wed, Jan 18, 2017 at 10:01:03AM -0500, James Bottomley wrote:
> > On Mon, 2017-01-16 at 15:12 +0200, Jarkko Sakkinen wrote:
> > > From: James Bottomley <James.Bottomley@...senPartnership.com>
> > >
> > > Currently the Resource Manager (RM) is not exposed to userspace.
> > > Make this exposure via a separate device, which can now be
> > > opened multiple times because each read/write transaction goes
> > > separately via the RM.
> > >
> > > Concurrency is protected by the chip->tpm_mutex for each
> > > read/write transaction separately. The TPM is cleared of all
> > > transient objects by the time the mutex is dropped, so there
> > > should be no interference between the kernel and userspace.
> >
> > There's actually a missing kfree of context_buf on the tpms_release
> > path as well. This patch fixes it up.
>
> Can you send me a fresh version of the whole patch so that I can
> include to v4 that includes also changes that I requested in my
> recent comments + all the fixes?
Sure, I think the attached is basically it
James
Download attachment "tmp.mail" of type "application/mbox" (9093 bytes)
Powered by blists - more mailing lists