Re: [PATCH 1/6] efistub: pass uefi secureboot flag via fdt params
From: Ard Biesheuvel <ardb@kernel.org>
Date: 2020-10-12 08:20:31
Also in:
linux-doc, linux-efi, linux-integrity, lkml
On Mon, 5 Oct 2020 at 04:20, Chester Lin [off-list ref] wrote:
On Mon, Sep 14, 2020 at 04:05:22PM +0800, Chester Lin wrote:quoted
Hi Ard, On Fri, Sep 11, 2020 at 06:01:09PM +0300, Ard Biesheuvel wrote:quoted
On Fri, 4 Sep 2020 at 10:29, Chester Lin [off-list ref] wrote:quoted
Add a new UEFI parameter: "linux,uefi-secure-boot" in fdt boot params as other architectures have done in their own boot data. For example, the boot_params->secure_boot in x86. Signed-off-by: Chester Lin <redacted>Why do we need this flag? Can't the OS simply check the variable directly?In fact, there's a difficulty to achieve this. When linux kernel is booting on ARM, the runtime services are enabled later on. It's done by arm_enable_runtime_services(), which is registered as an early_initcall. Before it calls efi_native_runtime_setup(), all EFI runtime callbacks are still NULL so calling efi.get_variable() will cause NULL pointer dereference. There's a case that arch_ima_get_secureboot() can be called in early boot stage. For example, when you try to set "ima_appraise=off" in kernel command line, it's actually handled early: [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/Image-5.9.0-rc3-9.gdd61cda- vanilla root=UUID=a88bfb80-8abb-425c-a0f3-ad317465c28b splash=silent mitigations =auto ignore_loglevel earlycon=pl011,mmio,0x9000000 console=ttyAMA0 ima_appraise=off [ 0.000000] ima: Secure boot enabled: ignoring ima_appraise=off boot parameter option [ 0.000000] Dentry cache hash table entries: 1048576 (order: 11, 8388608 bytes, linear) However EFI services are remapped and enabled afterwards. [ 0.082286] rcu: Hierarchical SRCU implementation. [ 0.089592] Remapping and enabling EFI services. [ 0.097509] smp: Bringing up secondary CPUs ... Another problem is that efi_rts_wq is created in subsys_initcall so we have to wait for both EFI services mapping and the workqueue get initiated before calling efi.get_variable() on ARM. The only way I can think of is to put a flag via fdt params. May I have your suggestions? I will appreciate if there's any better approach. Thanks, ChesterPing. May I have some suggestions here?
IMA itself is initialized as a late initcall. The only reason you see this message early is because this is where the parsing of the command line parameter happens. I'll send out a patch with a proposed solution for this issue. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel