From: Jarkko Sakkinen <jarkko@kernel.org>
To: Stefan Berger <stefanb@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org
Cc: jgg@ziepe.ca, linux-integrity@vger.kernel.org,
eajames@linux.ibm.com, peterhuewe@gmx.de,
yangyingliang@huawei.com
Subject: Re: [PATCH v2 1/2] powerpc/tpm: Create linux,sml-base/size as big endian
Date: Wed, 12 Jul 2023 00:54:31 +0300 [thread overview]
Message-ID: <ec564375084b6edd7b7d77eb341f451e798fb50d.camel@kernel.org> (raw)
In-Reply-To: <0fb26243-0d63-118b-2737-05391ba0c69a@linux.ibm.com>
On Tue, 2023-07-11 at 08:47 -0400, Stefan Berger wrote:
>
> On 7/10/23 17:23, Jarkko Sakkinen wrote:
> > On Thu, 2023-06-15 at 22:37 +1000, 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>
> > > ---
> > > arch/powerpc/kernel/prom_init.c | 8 ++++++--
> > > drivers/char/tpm/eventlog/of.c | 23 ++++-------------------
> > > 2 files changed, 10 insertions(+), 21 deletions(-)
> >
> > Split into two patches (producer and consumer).
>
> I think this wouldn't be right since it would break the system when only one patch is applied since it would be reading the fields in the wrong endianess.
I think it would help if the commit message would better explain
what is going on. It is somewhat difficult to decipher, if you
don't have deep knowledge of the powerpc architecture.
BR, Jarkko
next prev parent reply other threads:[~2023-07-11 21:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 12:37 [PATCH v2 1/2] powerpc/tpm: Create linux,sml-base/size as big endian Michael Ellerman
2023-06-15 12:37 ` [PATCH v2 2/2] powerpc/tpm: Reserve SML log when kexec'ing with kexec_file_load() Michael Ellerman
2023-06-19 0:26 ` Stefan Berger
2023-07-10 21:23 ` [PATCH v2 1/2] powerpc/tpm: Create linux,sml-base/size as big endian Jarkko Sakkinen
2023-07-11 12:47 ` Stefan Berger
2023-07-11 21:54 ` Jarkko Sakkinen [this message]
2023-07-12 12:39 ` Michael Ellerman
2023-07-17 13:13 ` Jarkko Sakkinen
2023-07-12 12:34 ` Michael Ellerman
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=ec564375084b6edd7b7d77eb341f451e798fb50d.camel@kernel.org \
--to=jarkko@kernel.org \
--cc=eajames@linux.ibm.com \
--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=stefanb@linux.ibm.com \
--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).