[PATCH v5 16/17] tpm: take TPM chip power gating out of tpm_transmit()

Winkler, Tomas tomas.winkler at intel.com
Tue Nov 13 11:58:58 UTC 2018



> -----Original Message-----
> From: Jarkko Sakkinen [mailto:jarkko.sakkinen at linux.intel.com]
> Sent: Tuesday, November 13, 2018 13:12
> To: Winkler, Tomas <tomas.winkler at intel.com>
> Cc: linux-integrity at vger.kernel.org; linux-security-module at vger.kernel.org;
> James Bottomley <James.Bottomley at HansenPartnership.com>; Struk,
> Tadeusz <tadeusz.struk at intel.com>; Stefan Berger
> <stefanb at linux.vnet.ibm.com>; Nayna Jain <nayna at linux.ibm.com>; Peter
> Huewe <peterhuewe at gmx.de>; Jason Gunthorpe <jgg at ziepe.ca>; Arnd
> Bergmann <arnd at arndb.de>; Greg Kroah-Hartman
> <gregkh at linuxfoundation.org>; open list <linux-kernel at vger.kernel.org>
> Subject: Re: [PATCH v5 16/17] tpm: take TPM chip power gating out of
> tpm_transmit()
> 
> On Fri, Nov 09, 2018 at 09:37:48PM +0000, Winkler, Tomas wrote:
> > > On Thu, Nov 08, 2018 at 06:38:59PM +0000, Winkler, Tomas wrote:
> > > > > Call tpm_chip_start() and tpm_chip_stop() in
> > > > >
> > > > > * tpm_try_get_ops() and tpm_put_ops()
> > > > > * tpm_chip_register()
> > > > > * tpm2_del_space()
> > > > >
> > > > > And remove these calls from tpm_transmit(). The core reason for
> > > > > this change is that in tpm_vtpm_proxy a locality change requires
> > > > > a virtual TPM command (a command made up just for that driver).
> > > > >
> > > > I don't think you can do that,  locality has to be request for
> > > > each command, as  for example tboot can request higher locality any
> time.
> > >
> > > That could be a potential problem. How tboot intervention gets
> > > prevented without this patch?
> > As it was said, need to request locality and relinquish it for each
> > command, I believe thought this is not required for client platforms
> > only for servers.
> 
> And what I'm trying to under is why so.
> 
> If the intervention can happen at any time that would imply that even if you
> would request and relinquish locality for a single TPM command, the
> intervention could happen in the middle. That is why I'm asking why without
> this patch things are just fine.
Yes, w/o this constrain it would be okay to request locality only once, 
we can ask tboot ask again but at the time the requirement was that locality can be taken of at any point, 
I believe that the locality won't be granted till a single command is completed.

Anyhow still the power gating is wrong in this patch do not ignore that part.

Thanks
Tomas



More information about the Linux-security-module-archive mailing list