[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <af61537d6d4b293813f86c4b55dcfe15a3139085.camel@linux.ibm.com>
Date: Wed, 26 Mar 2025 19:44:06 -0400
From: Mimi Zohar <zohar@...ux.ibm.com>
To: steven chen <chenste@...ux.microsoft.com>, Baoquan He <bhe@...hat.com>
Cc: stefanb@...ux.ibm.com, roberto.sassu@...weicloud.com,
roberto.sassu@...wei.com, eric.snowberg@...cle.com,
ebiederm@...ssion.com, paul@...l-moore.com, code@...icks.com,
bauermann@...abnow.com, linux-integrity@...r.kernel.org,
kexec@...ts.infradead.org, linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, madvenka@...ux.microsoft.com,
nramas@...ux.microsoft.com, James.Bottomley@...senpartnership.com,
vgoyal@...hat.com, dyoung@...hat.com
Subject: Re: [PATCH v10 6/8] ima: kexec: move IMA log copy from kexec load
to execute
> > Hmm, it's easier, while maybe not good. We should not repeatedly
> > introduce similar things into codes. Here, it's similar as
> > what kexec_apply_relocations() and arch_kexec_apply_relocations() are
> > doing.
> >
> > int machine_kexec_post_load(struct kimage *image)
(As discussed) just as kexec_apply_relocation calls
arch_kexec_apply_relocations(). Name this function kexec_post_load() and call
machine_kexec_post_load().
Mimi
> > {
> > #ifdef CONFIG_IMA_KEXEC
> > ima_kexec_post_load(image);
> > #endif
> > return arch_machine_kexec_post_load();
> > }
>
Powered by blists - more mailing lists