All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nayna <nayna@linux.vnet.ibm.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: tpmdd-devel@lists.sourceforge.net, peterhuewe@gmx.de,
	tpmdd@selhorst.net, jgunthorpe@obsidianresearch.com,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/2] tpm: enhance read_log_of() to support Physical TPM event log
Date: Fri, 16 Dec 2016 21:58:13 +0530	[thread overview]
Message-ID: <5854161D.6010006@linux.vnet.ibm.com> (raw)
In-Reply-To: <20161212144004.ojrbp6e3whxyydi4@intel.com>



On 12/12/2016 08:10 PM, Jarkko Sakkinen wrote:
> On Sun, Dec 11, 2016 at 12:35:32AM -0500, Nayna Jain wrote:
>> Physical TPMs use Open Firmware Device Tree bindings that are similar
>> to the IBM Power virtual TPM to support event log. However, these
>> properties store the values in different endianness for Physical
>> and Virtual TPM.
>>
>> This patch fixes the endianness issue by doing appropriate conversion
>> based on Physical or Virtual TPM.
>
> Will other device tree using firmwares than OF use the same bindings?

Yes, that is what expected that all other device tree using firmware 
will also use same bindings.

Thanks & Regards,
     - Nayna

>
>> Signed-off-by: Nayna Jain <nayna@linux.vnet.ibm.com>
>> ---
>>   drivers/char/tpm/tpm_of.c | 27 +++++++++++++++++++++++----
>>   1 file changed, 23 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/char/tpm/tpm_of.c b/drivers/char/tpm/tpm_of.c
>> index 7dee42d7..de57d4a 100644
>> --- a/drivers/char/tpm/tpm_of.c
>> +++ b/drivers/char/tpm/tpm_of.c
>> @@ -27,6 +27,8 @@ int tpm_read_log_of(struct tpm_chip *chip)
>>   	const u32 *sizep;
>>   	const u64 *basep;
>>   	struct tpm_bios_log *log;
>> +	u32 size;
>> +	u64 base;
>>
>>   	log = &chip->log;
>>   	if (chip->dev.parent && chip->dev.parent->of_node)
>> @@ -41,18 +43,35 @@ int tpm_read_log_of(struct tpm_chip *chip)
>>   	if (sizep == NULL || basep == NULL)
>>   		return -EIO;
>>
>> -	if (*sizep == 0) {
>> +	/*
>> +	 * For both vtpm/tpm, firmware has log addr and log size in big
>> +	 * endian format. But in case of vtpm, there is a method called
>> +	 * sml-handover which is run during kernel init even before
>> +	 * device tree is setup. This sml-handover function takes care
>> +	 * of endianness and writes to sml-base and sml-size in little
>> +	 * endian format. For this reason, vtpm doesn't need conversion
>> +	 * but physical tpm needs the conversion.
>> +	 */
>> +	if (of_property_match_string(np, "compatible", "IBM,vtpm") < 0) {
>> +		size = be32_to_cpup(sizep);
>> +		base = be64_to_cpup(basep);
>> +	} else {
>> +		size = *sizep;
>> +		base = *basep;
>> +	}
>> +
>> +	if (size == 0) {
>>   		dev_warn(&chip->dev, "%s: Event log area empty\n", __func__);
>>   		return -EIO;
>>   	}
>>
>> -	log->bios_event_log = kmalloc(*sizep, GFP_KERNEL);
>> +	log->bios_event_log = kmalloc(size, GFP_KERNEL);
>>   	if (!log->bios_event_log)
>>   		return -ENOMEM;
>>
>> -	log->bios_event_log_end = log->bios_event_log + *sizep;
>> +	log->bios_event_log_end = log->bios_event_log + size;
>>
>> -	memcpy(log->bios_event_log, __va(*basep), *sizep);
>> +	memcpy(log->bios_event_log, __va(base), size);
>>
>>   	return 0;
>>   }
>> --
>> 2.5.0
>>
>
> Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
>
> /Jarkko
>


  reply	other threads:[~2016-12-16 16:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-11  5:35 [PATCH v7 0/2] securityfs support for TPM 2.0 firmware event log Nayna Jain
2016-12-11  5:35 ` Nayna Jain
     [not found] ` <1481434533-3453-1-git-send-email-nayna-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2016-12-11  5:35   ` [PATCH v7 1/2] tpm: enhance read_log_of() to support Physical TPM " Nayna Jain
2016-12-11  5:35     ` Nayna Jain
2016-12-12 14:40     ` Jarkko Sakkinen
2016-12-16 16:28       ` Nayna [this message]
2016-12-11  5:35   ` [PATCH v7 2/2] tpm: add securityfs support for TPM 2.0 firmware " Nayna Jain
2016-12-11  5:35     ` Nayna Jain
     [not found]     ` <1481434533-3453-3-git-send-email-nayna-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-01-02 22:12       ` Jarkko Sakkinen
2017-01-02 22:12         ` Jarkko Sakkinen
2017-01-03  7:39         ` Nayna
     [not found]           ` <586B5526.9090703-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-01-03 13:33             ` Jarkko Sakkinen
2017-01-03 13:33               ` Jarkko Sakkinen
     [not found]               ` <20170103133309.lt5k4c37rjq5vcbq-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-01-04  8:38                 ` Nayna
2017-01-04  8:38                   ` Nayna
     [not found]                   ` <586CB46E.8050207-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-01-04 13:01                     ` Jarkko Sakkinen
2017-01-04 13:01                       ` 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=5854161D.6010006@linux.vnet.ibm.com \
    --to=nayna@linux.vnet.ibm.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=tpmdd-devel@lists.sourceforge.net \
    --cc=tpmdd@selhorst.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.