[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aEmxaJQNfYJwSCd0@kernel.org>
Date: Wed, 11 Jun 2025 19:40:08 +0300
From: Jarkko Sakkinen <jarkko@...nel.org>
To: Yeoreum Yun <yeoreum.yun@....com>
Cc: sudeep.holla@....com, peterhuewe@....de, jgg@...pe.ca,
stuart.yoder@....com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-integrity@...r.kernel.org
Subject: Re: [PATCH v2 0/2] fix failure of integration IMA with tpm_crb_ffa
On Tue, Jun 10, 2025 at 04:22:04PM +0100, Yeoreum Yun wrote:
> > OK, if ffa_init() is leveled up in the initcall hierarchy, shouldn't
> > that be enough as long as ko's can be found from initramfs?
>
> As you mentioned, this is handled in Patch #1.
> However, although ffa_init() is called first,
> unless tpm_crb_ffa_init() is also invoked,
> crb_acpi_driver_init() will fail with -EPROBE_DEFER.
>
> Please note that IMA is always built-in and cannot be built as a module.
Sure but if one needs IMA, then tpm_crb_ffa can be compiled as built-in
with zero code changes.
BR, Jarkko
Powered by blists - more mailing lists