[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170130214905.4bkvv2yrmzprn2la@intel.com>
Date: Mon, 30 Jan 2017 23:49:05 +0200
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Nayna <nayna@...ux.vnet.ibm.com>
Cc: Kenneth Goldman <kgoldman@...ibm.com>,
"moderated list:TPM DEVICE DRIVER"
<tpmdd-devel@...ts.sourceforge.net>,
open list <linux-kernel@...r.kernel.org>,
linux-security-module@...r.kernel.org
Subject: Re: Fwd: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs
support,for TPM 2.0 firmware event log
On Mon, Jan 30, 2017 at 03:08:42PM +0530, Nayna wrote:
>
> > From: "Ken Goldman" <kgold@...ux.vnet.ibm.com
> > <mailto:kgold@...ux.vnet.ibm.com>>
> > Date: 26-Jan-2017 2:53 AM
> > Subject: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs
> > support,for TPM 2.0 firmware event log
> > To: <linux-kernel@...r.kernel.org
> > <mailto:linux-kernel@...r.kernel.org>>,
> > <linux-security-module@...r.kernel.org
> > <mailto:linux-security-module@...r.kernel.org>>,
> > <tpmdd-devel@...ts.sourceforge.net
> > <mailto:tpmdd-devel@...ts.sourceforge.net>>
> > Cc:
> >
> > You do not need to send a new patch set version as long as this
> > one gets peer tested. And it needs to be tested without hacks
> > like plumbing TCPA with TPM 2.0 in QEMU. OF code paths needs to
> > be peer tested to be more specific.
> >
> > For me the code itself looks good but I simply cannot take it in
> > in the current situation.
> >
> > /Jarkko
> >
> >
> > Tested-by: Kenneth Goldman <kgold@...ux.vnet.ibm.com
> > <mailto:kgold@...ux.vnet.ibm.com>>
> >
> > I validated a firmware event log taken from a Power 8 against PCR 0-7
> > values for the SHA-1 and SHA-256 banks from a Nuvoton TPM 2.0 chip on
> > that same platform.
> >
>
> Thank You Ken.
>
> Jarkko, I hope now these patches can be accepted for 4.11.
>
> Thanks & Regards,
> - Nayna
Thanks Ken. I somehow managed to miss that response.
/Jarkko
Powered by blists - more mailing lists