linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: steven chen <chenste@linux.microsoft.com>
Cc: zohar@linux.ibm.com, stefanb@linux.ibm.com,
	roberto.sassu@huaweicloud.com, roberto.sassu@huawei.com,
	eric.snowberg@oracle.com, ebiederm@xmission.com,
	paul@paul-moore.com, code@tyhicks.com, bauermann@kolabnow.com,
	linux-integrity@vger.kernel.org, kexec@lists.infradead.org,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, madvenka@linux.microsoft.com,
	nramas@linux.microsoft.com,
	James.Bottomley@hansenpartnership.com, vgoyal@redhat.com,
	dyoung@redhat.com
Subject: Re: [PATCH v8 2/7] kexec: define functions to map and unmap segments
Date: Mon, 24 Feb 2025 14:14:22 +0800	[thread overview]
Message-ID: <Z7wOPiDfy/vtrkCS@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20250218225502.747963-3-chenste@linux.microsoft.com>

Hi Steve, Mimi,

On 02/18/25 at 02:54pm, steven chen wrote:
> Currently, the mechanism to map and unmap segments to the kimage
> structure is not available to the subsystems outside of kexec.  This
> functionality is needed when IMA is allocating the memory segments
> during kexec 'load' operation.  Implement functions to map and unmap
> segments to kimage.

I am done with the whole patchset understanding. My concern is if this
TPM PCRs content can be carried over through newly introduced KHO. I can
see that these patchset doesn't introduce too much new code changes,
while if many conponents need do this, kexec reboot will be patched all
over its body and become ugly and hard to maintain.

Please check Mike Rapoport's v4 patchset to see if IMA can register
itself to KHO and do somthing during 2nd kernel init to restore those
TPM PCRs content to make sure all measurement logs are read correctly.
[PATCH v4 00/14] kexec: introduce Kexec HandOver (KHO)

Thanks
Baoquan


  parent reply	other threads:[~2025-02-24  6:14 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18 22:54 [PATCH v8 0/7] ima: kexec: measure events between kexec load and execute steven chen
2025-02-18 22:54 ` [PATCH v8 1/7] ima: define and call ima_alloc_kexec_file_buf steven chen
2025-02-20 14:53   ` Mimi Zohar
2025-02-20 15:04     ` James Bottomley
2025-02-20 16:23       ` Mimi Zohar
2025-02-21 21:02         ` steven chen
2025-02-18 22:54 ` [PATCH v8 2/7] kexec: define functions to map and unmap segments steven chen
2025-02-20  0:53   ` kernel test robot
2025-02-20 17:22   ` Mimi Zohar
2025-02-21 21:05     ` steven chen
2025-02-24  6:14   ` Baoquan He [this message]
2025-02-24 23:05     ` steven chen
2025-02-25  0:18       ` Baoquan He
2025-02-25 18:35         ` steven chen
2025-02-26  0:39           ` Baoquan He
2025-02-27 15:41     ` Mimi Zohar
2025-02-28  5:03       ` Baoquan He
2025-03-04 16:15         ` Mimi Zohar
2025-02-18 22:54 ` [PATCH v8 3/7] ima: kexec: skip IMA segment validation after kexec soft reboot steven chen
2025-02-21 15:41   ` Mimi Zohar
2025-02-21 21:06     ` steven chen
2025-02-18 22:54 ` [PATCH v8 4/7] ima: kexec: define functions to copy IMA log at soft boot steven chen
2025-02-19 15:37   ` Stefan Berger
2025-02-19 19:21     ` steven chen
2025-02-21 19:07   ` Mimi Zohar
2025-02-21 19:41     ` Stefan Berger
2025-02-18 22:55 ` [PATCH v8 5/7] ima: kexec: move IMA log copy from kexec load to execute steven chen
2025-02-19 15:57   ` Stefan Berger
2025-02-19 19:23     ` steven chen
2025-02-20  1:35   ` kernel test robot
2025-02-18 22:55 ` [PATCH v8 6/7] ima: make the kexec extra memory configurable steven chen
2025-02-20 21:36   ` Mimi Zohar
2025-02-18 22:55 ` [PATCH v8 7/7] ima: measure kexec load and exec events as critical data steven chen
2025-02-19 16:23   ` Stefan Berger
2025-02-19 19:24     ` steven chen
2025-02-21  0:46   ` Mimi Zohar
2025-02-21 21:10     ` steven chen

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=Z7wOPiDfy/vtrkCS@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=bauermann@kolabnow.com \
    --cc=chenste@linux.microsoft.com \
    --cc=code@tyhicks.com \
    --cc=dyoung@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=eric.snowberg@oracle.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=madvenka@linux.microsoft.com \
    --cc=nramas@linux.microsoft.com \
    --cc=paul@paul-moore.com \
    --cc=roberto.sassu@huawei.com \
    --cc=roberto.sassu@huaweicloud.com \
    --cc=stefanb@linux.ibm.com \
    --cc=vgoyal@redhat.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).