From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: Nayna Jain <nayna@linux.vnet.ibm.com>, tpmdd-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [tpmdd-devel] [PATCH v8 2/2] tpm: add securityfs support for TPM 2.0 firmware event log
Date: Fri, 13 Jan 2017 15:35:40 -0500 [thread overview]
Message-ID: <9e823fb6-dcc7-a097-1cba-948aeffe2eb6@linux.vnet.ibm.com> (raw)
In-Reply-To: <9c605b61-bd5f-eb74-8fc0-ac3587852808@linux.vnet.ibm.com>
On 01/13/2017 01:09 PM, Stefan Berger wrote:
> On 01/11/2017 02:54 AM, Nayna Jain wrote:
>> Unlike the device driver support for TPM 1.2, the TPM 2.0 does
>> not support the securityfs pseudo files for displaying the
>> firmware event log.
>>
>> This patch enables support for providing the TPM 2.0 event log in
>> binary form. TPM 2.0 event log supports a crypto agile format that
>> records multiple digests, which is different from TPM 1.2. This
>> patch enables the tpm_bios_log_setup for TPM 2.0 and adds the
>> event log parser which understand the TPM 2.0 crypto agile format.
>>
>> Signed-off-by: Nayna Jain <nayna@linux.vnet.ibm.com>
>> ---
>> drivers/char/tpm/Makefile | 2 +-
>> .../char/tpm/{tpm_eventlog.c => tpm1_eventlog.c} | 35 ++--
>> drivers/char/tpm/tpm2_eventlog.c | 203
>> +++++++++++++++++++++
>> drivers/char/tpm/tpm_acpi.c | 3 +
>> drivers/char/tpm/tpm_eventlog.h | 63 +++++++
>> 5 files changed, 291 insertions(+), 15 deletions(-)
>> rename drivers/char/tpm/{tpm_eventlog.c => tpm1_eventlog.c} (95%)
>> create mode 100644 drivers/char/tpm/tpm2_eventlog.c
>>
>>
>> diff --git a/drivers/char/tpm/tpm_acpi.c b/drivers/char/tpm/tpm_acpi.c
>> index b7718c9..169edf3 100644
>> --- a/drivers/char/tpm/tpm_acpi.c
>> +++ b/drivers/char/tpm/tpm_acpi.c
>> @@ -54,6 +54,9 @@ int tpm_read_log_acpi(struct tpm_chip *chip)
>> u64 len, start;
>> struct tpm_bios_log *log;
>>
>> + if (chip->flags & TPM_CHIP_FLAG_TPM2)
>> + return -ENODEV;
>> +
>
>
> Works with SeaBIOS when this check is disabled.
>
-> Tested-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
next prev parent reply other threads:[~2017-01-13 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 7:54 [PATCH v8 0/2] " Nayna Jain
2017-01-11 7:54 ` [PATCH v8 1/2] tpm: enhance read_log_of() to support Physical TPM " Nayna Jain
2017-01-11 7:54 ` [PATCH v8 2/2] tpm: add securityfs support for TPM 2.0 firmware " Nayna Jain
2017-01-12 17:41 ` Jarkko Sakkinen
2017-01-13 18:09 ` [tpmdd-devel] " Stefan Berger
2017-01-13 20:35 ` Stefan Berger [this message]
2017-01-16 9:38 ` 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=9e823fb6-dcc7-a097-1cba-948aeffe2eb6@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=nayna@linux.vnet.ibm.com \
--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
all inboxes | Powered by JetHome®