devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Berger <stefanb@linux.ibm.com>
To: Borislav Petkov <bp@suse.de>
Cc: kexec@lists.infradead.org, devicetree@vger.kernel.org,
	linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, nayna@linux.ibm.com,
	nasastry@in.ibm.com, mpe@ellerman.id.au,
	Jonathan McDowell <noodles@fb.com>,
	Mimi Zohar <zohar@linux.ibm.com>
Subject: Re: [PATCH v7 3/6] x86/kexec: Carry forward IMA measurement log on kexec
Date: Fri, 12 Aug 2022 13:14:38 -0400	[thread overview]
Message-ID: <935988a4-c245-7cb1-4e14-bc99d39220a1@linux.ibm.com> (raw)
In-Reply-To: <YvaJc7bQjz61Y1jj@zn.tnic>



On 8/12/22 13:10, Borislav Petkov wrote:
> On Fri, Aug 12, 2022 at 12:43:02PM -0400, Stefan Berger wrote:
>> From: Jonathan McDowell <noodles@fb.com>
>>
>> On kexec file load, the Integrity Measurement Architecture (IMA)
>> subsystem may verify the IMA signature of the kernel and initramfs, and
>> measure it. The command line parameters passed to the kernel in the
>> kexec call may also be measured by IMA.
>>
>> A remote attestation service can verify a TPM quote based on the TPM
>> event log, the IMA measurement list and the TPM PCR data. This can
>> be achieved only if the IMA measurement log is carried over from the
>> current kernel to the next kernel across the kexec call.
>>
>> PowerPC and ARM64 both achieve this using device tree with a
>> "linux,ima-kexec-buffer" node. x86 platforms generally don't make use of
>> device tree, so use the setup_data mechanism to pass the IMA buffer to
>> the new kernel.
>>
>> Signed-off-by: Jonathan McDowell <noodles@fb.com>
>> Signed-off-by: Borislav Petkov <bp@suse.de>
>> Reviewed-by: Mimi Zohar <zohar@linux.ibm.com> # IMA function definitions
>> Link: https://lore.kernel.org/r/YmKyvlF3my1yWTvK@noodles-fedora-PC23Y6EG
> 
> Is there any particular reason to keep sending a patch which is already
> upstream?
> 

Yes, so this series can be tested by krobot. I only based this series on 
5.19 so far, so if it's upstreamed since then it will go missing next 
time when I base  it on 5.20-rc1 or so.

  reply	other threads:[~2022-08-12 17:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-12 16:42 [PATCH v7 0/6] tpm: Preserve TPM measurement log across kexec (ppc64) Stefan Berger
2022-08-12 16:43 ` [PATCH v7 1/6] of: check previous kernel's ima-kexec-buffer against memory bounds Stefan Berger
2022-08-12 16:43 ` [PATCH v7 2/6] drivers: of: kexec ima: Support 32-bit platforms Stefan Berger
2022-08-12 16:43 ` [PATCH v7 3/6] x86/kexec: Carry forward IMA measurement log on kexec Stefan Berger
2022-08-12 17:10   ` Borislav Petkov
2022-08-12 17:14     ` Stefan Berger [this message]
2022-08-12 18:28       ` Borislav Petkov
2022-08-12 16:43 ` [PATCH v7 4/6] tpm: of: Make of-tree specific function commonly available Stefan Berger
2022-08-14 19:16   ` Jarkko Sakkinen
2022-08-14 19:16     ` Jarkko Sakkinen
2022-08-12 16:43 ` [PATCH v7 5/6] of: kexec: Refactor IMA buffer related functions to make them reusable Stefan Berger
2022-08-12 16:43 ` [PATCH v7 6/6] tpm/kexec: Duplicate TPM measurement log in of-tree for kexec Stefan Berger
2022-08-22 17:59   ` Rob Herring
2022-08-15  6:48 ` [PATCH v7 0/6] tpm: Preserve TPM measurement log across kexec (ppc64) Coiby Xu
2022-08-15  6:53   ` Coiby Xu
2022-08-15 13:32   ` 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=935988a4-c245-7cb1-4e14-bc99d39220a1@linux.ibm.com \
    --to=stefanb@linux.ibm.com \
    --cc=bp@suse.de \
    --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 \
    --cc=noodles@fb.com \
    --cc=zohar@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).