From: Stefan Berger <stefanb@linux.ibm.com>
To: kexec@lists.infradead.org, devicetree@vger.kernel.org,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Cc: nayna@linux.ibm.com, nasastry@in.ibm.com, mpe@ellerman.id.au,
Stefan Berger <stefanb@linux.ibm.com>
Subject: [PATCH v3 0/3] tpm: Preserve TPM measurement log across kexec (ppc64)
Date: Tue, 28 Jun 2022 12:58:17 -0400 [thread overview]
Message-ID: <20220628165820.883222-1-stefanb@linux.ibm.com> (raw)
The of-tree subsystem does not currently preserve the IBM vTPM 1.2 and
vTPM 2.0 measurement logs across a kexec on ppc64. This series fixes this
for the kexec_file_load() syscall using the flattened device tree (fdt) to
carry the measurement log's buffer across kexec.
Stefan
Stefan Berger (3):
tpm: of: Make of-tree specific function commonly available
of: kexec: Refactor IMA buffer related functions to make them reusable
tpm/kexec: Duplicate TPM measurement log in of-tree for kexec
drivers/char/Makefile | 1 +
drivers/char/tpm/Makefile | 1 +
drivers/char/tpm/eventlog/of.c | 31 +--
drivers/char/tpm/eventlog/tpm_of.c | 27 +++
drivers/of/kexec.c | 293 +++++++++++++++++++++++++----
include/linux/kexec.h | 6 +
include/linux/of.h | 8 +-
include/linux/tpm.h | 5 +
kernel/kexec_file.c | 6 +
9 files changed, 315 insertions(+), 63 deletions(-)
create mode 100644 drivers/char/tpm/eventlog/tpm_of.c
--
2.35.1
next reply other threads:[~2022-06-28 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 16:58 Stefan Berger [this message]
2022-06-28 16:58 ` [PATCH v3 1/3] tpm: of: Make of-tree specific function commonly available Stefan Berger
2022-06-28 16:58 ` [PATCH v3 2/3] of: kexec: Refactor IMA buffer related functions to make them reusable Stefan Berger
2022-06-28 16:58 ` [PATCH v3 3/3] tpm/kexec: Duplicate TPM measurement log in of-tree for kexec Stefan Berger
2022-06-28 17:25 ` [PATCH v3 0/3] tpm: Preserve TPM measurement log across kexec (ppc64) Stefan Berger
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=20220628165820.883222-1-stefanb@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=devicetree@vger.kernel.org \
--cc=kexec@lists.infradead.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nasastry@in.ibm.com \
--cc=nayna@linux.ibm.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).