From: Stefan Berger <stefanb@linux.ibm.com>
To: Rob Herring <robh@kernel.org>
Cc: kexec@lists.infradead.org, devicetree@vger.kernel.org,
linux-integrity@vger.kernel.org, nayna@linux.ibm.com,
nasastry@in.ibm.com
Subject: Re: [PATCH v2 0/3] tpm: Preserve TPM measurement log across kexec
Date: Tue, 28 Jun 2022 08:45:40 -0400 [thread overview]
Message-ID: <01b52288-7fb4-3b4c-4e47-1f74a839818e@linux.ibm.com> (raw)
In-Reply-To: <20220627223352.GA3082294-robh@kernel.org>
On 6/27/22 18:33, Rob Herring wrote:
> On Thu, Jun 16, 2022 at 11:41:27AM -0400, Stefan Berger wrote:
>> The of-tree driver does not currently preserve the IBM vTPM 1.2 and
>> vTPM 2.0 measurement logs across a kexec. 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.
>
> As mentioned in v1, please Cc other folks that might care about TPMs
> and kexec. I'm sure it's not only IBM.
That's why I cc'ed the linux-integrity mailing list now where all the
TPM related development is happening.
Stefan
>
> Rob
prev parent reply other threads:[~2022-06-28 12:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 15:41 [PATCH v2 0/3] tpm: Preserve TPM measurement log across kexec Stefan Berger
2022-06-16 15:41 ` [PATCH v2 1/3] tpm: of: Move of-tree specific code from tpm driver into of driver Stefan Berger
2022-06-27 22:43 ` Rob Herring
2022-06-28 13:29 ` Stefan Berger
2022-06-29 2:45 ` Jarkko Sakkinen
2022-06-29 14:16 ` Stefan Berger
2022-06-30 23:16 ` Jarkko Sakkinen
2022-06-16 15:41 ` [PATCH v2 2/3] of: kexec: Refactor IMA buffer related functions to make them reusable Stefan Berger
2022-06-16 15:41 ` [PATCH v2 3/3] tpm/kexec: Duplicate TPM measurement log in of-tree for kexec Stefan Berger
2022-06-16 20:25 ` kernel test robot
2022-06-28 16:53 ` kernel test robot
2022-06-27 22:33 ` [PATCH v2 0/3] tpm: Preserve TPM measurement log across kexec Rob Herring
2022-06-28 12:45 ` Stefan Berger [this message]
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=01b52288-7fb4-3b4c-4e47-1f74a839818e@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=nasastry@in.ibm.com \
--cc=nayna@linux.ibm.com \
--cc=robh@kernel.org \
/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).