Thomas Gleixner b6872b4a7d x86/efi: Make efi_set_virtual_address_map IBT safe ... [ Upstream commit 0303c9729a ] Niklāvs reported a boot regression on an Alderlake machine and bisected it to commit 9df9d2f047 ("init: Invoke arch_cpu_finalize_init() earlier"). By moving the invocation of arch_cpu_finalize_init() further down he identified that efi_enter_virtual_mode() is the function which causes the boot hang. The main difference of the earlier invocation is that the boot CPU is already fully initialized and mitigations and alternatives are applied. But the only really interesting change turned out to be IBT, which is now enabled before efi_enter_virtual_mode(). "ibt=off" on the kernel command line cured the problem. Inspection of the involved calls in efi_enter_virtual_mode() unearthed that efi_set_virtual_address_map() is the only place in the kernel which invokes an EFI call without the IBT safe wrapper. This went obviously unnoticed so far as IBT was enabled later. Use arch_efi_call_virt() instead of efi_call() to cure that. Fixes: fe379fa4d1 ("x86/ibt: Disable IBT around firmware") Fixes: 9df9d2f047 ("init: Invoke arch_cpu_finalize_init() earlier") Reported-by: Niklāvs Koļesņikovs <pinkflames.linux@gmail.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Ard Biesheuvel <ardb@kernel.org> Link: https://bugzilla.kernel.org/show_bug.cgi?id=217602 Link: https://lore.kernel.org/r/87jzvm12q0.ffs@tglx Signed-off-by: Sasha Levin <sashal@kernel.org>		2023-07-19 16:21:45 +02:00
..
Makefile	…
efi.c	…
efi_32.c	…
efi_64.c	x86/efi: Make efi_set_virtual_address_map IBT safe	2023-07-19 16:21:45 +02:00
efi_stub_32.S	…
efi_stub_64.S	…
efi_thunk_64.S	efi/x86-mixed: move unmitigated RET into .rodata	2022-08-16 09:28:05 +02:00
quirks.c	…