public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nayna <nayna@linux.vnet.ibm.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Kenneth Goldman <kgoldman@us.ibm.com>,
	"moderated list:TPM DEVICE DRIVER" 
	<tpmdd-devel@lists.sourceforge.net>,
	open list <linux-kernel@vger.kernel.org>,
	linux-security-module@vger.kernel.org
Subject: Re: Fwd: Re: [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support,for TPM 2.0 firmware event log
Date: Wed, 1 Feb 2017 00:14:12 +0530	[thread overview]
Message-ID: <5890DAFC.9030407@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170131174659.b6njebycqzd5ur6f@intel.com>



On 01/31/2017 11:16 PM, Jarkko Sakkinen wrote:
> On Mon, Jan 30, 2017 at 03:08:42PM +0530, Nayna wrote:
>>
>>> From: "Ken Goldman" <kgold@linux.vnet.ibm.com
>>> <mailto:kgold@linux.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@vger.kernel.org
>>> <mailto:linux-kernel@vger.kernel.org>>,
>>> <linux-security-module@vger.kernel.org
>>> <mailto:linux-security-module@vger.kernel.org>>,
>>> <tpmdd-devel@lists.sourceforge.net
>>> <mailto:tpmdd-devel@lists.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@linux.vnet.ibm.com
>>> <mailto:kgold@linux.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
>
> I already sent my pull request to 4.11 and even today I found something
> fishy. You declared a function local array by using a variable in "tpm:
> enhance TPM 2.0 PCR extend to support multiple banks" (max_active_banks
> or something). And the event log patches have just passed the review.

Yes. I have checked using clang and it has passed the clang.. and I also 
verified there were no complains during build.

What type of problem do you see ?

Also, to understand, this is related to multi-bank patchset. I mean how 
does it affect for event log patchset ?

Thanks & Regards,
    - Nayna

>
> I've applied them to my tree but I'll only include bug fixes for 4.11
> pull requests. You'll have to wait till' 4.12.
>
> /Jarkko
>

  reply	other threads:[~2017-01-31 20:56 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 21:22 [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support,for TPM 2.0 firmware event log Ken Goldman
2017-01-25 23:06 ` Jarkko Sakkinen
     [not found] ` <CALAzByG474T_qSJ0Kry1LiNSsCQAHUagqcqtR_CnpporicZrdg@mail.gmail.com>
2017-01-30  9:38   ` Fwd: " Nayna
2017-01-30 21:49     ` Jarkko Sakkinen
2017-01-31 17:46     ` Jarkko Sakkinen
2017-01-31 18:44       ` Nayna [this message]
2017-01-31 20:50         ` Jarkko Sakkinen
2017-02-01  7:31           ` Nayna
2017-02-01 18:27             ` Jarkko Sakkinen
2017-02-01 14:48           ` Jarkko Sakkinen
2017-02-01 14:54             ` Jarkko Sakkinen
2017-02-01 19:25               ` Nayna
2017-02-01 19:50                 ` Jarkko Sakkinen
2017-01-31 20:34       ` Jarkko Sakkinen
2017-01-31 21:46         ` James Morris
2017-01-31 22:31           ` Jarkko Sakkinen
2017-01-31 22:31           ` Mimi Zohar
2017-02-01 10:30             ` Jarkko Sakkinen
2017-02-01 13:49               ` Mimi Zohar
2017-02-01 18:23                 ` Jarkko Sakkinen
2017-01-31 13:13 ` [tpmdd-devel] [PATCH v9 2/2] tpm: add securityfs support, for " 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=5890DAFC.9030407@linux.vnet.ibm.com \
    --to=nayna@linux.vnet.ibm.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=kgoldman@us.ibm.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