linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Berger <stefanb@linux.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org
Cc: eajames@linux.ibm.com, jgg@ziepe.ca, jarkko@kernel.org,
	yangyingliang@huawei.com, linux-integrity@vger.kernel.org,
	peterhuewe@gmx.de
Subject: Re: [PATCH 1/2] powerpc/tpm: Create linux,sml-base/size as big endian
Date: Mon, 27 Feb 2023 18:08:31 -0500	[thread overview]
Message-ID: <c2afd163-5f23-acab-fd39-3a5593ed6257@linux.ibm.com> (raw)
In-Reply-To: <20230224032508.3331281-1-mpe@ellerman.id.au>



On 2/23/23 22:25, Michael Ellerman wrote:
> There's code in prom_instantiate_sml() to do a "SML handover" (Stored
> Measurement Log) from OF to Linux, before Linux shuts down Open
> Firmware.
> 
> This involves creating a buffer to hold the SML, and creating two device
> tree properties to record its base address and size. The kernel then
> later reads those properties from the device tree to find the SML.
> 
> When the code was initially added in commit 4a727429abec ("PPC64: Add
> support for instantiating SML from Open Firmware") the powerpc kernel
> was always built big endian, so the properties were created big endian
> by default.
> 
> However since then little endian support was added to powerpc, and now
> the code lacks conversions to big endian when creating the properties.
> 
> This means on little endian kernels the device tree properties are
> little endian, which is contrary to the device tree spec, and in
> contrast to all other device tree properties.
> 
> To cope with that a workaround was added in tpm_read_log_of() to skip
> the endian conversion if the properties were created via the SML
> handover.
> 
> A better solution is to encode the properties as big endian as they
> should be, and remove the workaround.
> 
> Typically changing the encoding of a property like this would present
> problems for kexec. However the SML is not propagated across kexec, so
> changing the encoding of the properties is a non-issue.
> 
> Fixes: e46e22f12b19 ("tpm: enhance read_log_of() to support Physical TPM event log")
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>

Reviewed-by: Stefan Berger <stefanb@linux.ibm.com>

  parent reply	other threads:[~2023-02-27 23:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24  3:25 [PATCH 1/2] powerpc/tpm: Create linux,sml-base/size as big endian Michael Ellerman
2023-02-24  3:25 ` [PATCH 2/2] powerpc/tpm: Reserve SML log when kexec'ing Michael Ellerman
2023-02-28 19:18   ` Stefan Berger
2023-03-02 22:05     ` Michael Ellerman
2023-02-27 23:08 ` Stefan Berger [this message]
2023-02-28  3:10   ` [PATCH 1/2] powerpc/tpm: Create linux,sml-base/size as big endian Jarkko Sakkinen
2023-02-28 11:21     ` Michael Ellerman
2023-03-01 23:09       ` 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=c2afd163-5f23-acab-fd39-3a5593ed6257@linux.ibm.com \
    --to=stefanb@linux.ibm.com \
    --cc=eajames@linux.ibm.com \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=peterhuewe@gmx.de \
    --cc=yangyingliang@huawei.com \
    /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;
as well as URLs for NNTP newsgroup(s).