a7a6a01f88
The recently introduced EFI memory attributes protocol should be used
if it exists to ensure that the memory allocation created for the kernel
permits execution. This is needed for compatibility with tightened
requirements related to Windows logo certification for x86 PCs.
Currently, we simply strip the execute protect (XP) attribute from the
entire range, but this might be rejected under some firmware security
policies, and so in a subsequent patch, this will be changed to only
strip XP from the executable region that runs early, and make it
read-only (RO) as well.
In order to catch any issues early, ensure that the memory attribute
protocol works as intended, and give up if it produces spurious errors.
Note that the DXE services based fallback was always based on best
effort, so don't propagate any errors returned by that API.
Fixes: a1b87d54f4 ("x86/efistub: Avoid legacy decompressor when doing EFI boot")
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
17 lines
495 B
C
17 lines
495 B
C
/* SPDX-License-Identifier: GPL-2.0-only */
|
|
|
|
#include <linux/efi.h>
|
|
|
|
extern void trampoline_32bit_src(void *, bool);
|
|
extern const u16 trampoline_ljmp_imm_offset;
|
|
|
|
efi_status_t efi_adjust_memory_range_protection(unsigned long start,
|
|
unsigned long size);
|
|
|
|
#ifdef CONFIG_X86_64
|
|
efi_status_t efi_setup_5level_paging(void);
|
|
void efi_5level_switch(void);
|
|
#else
|
|
static inline efi_status_t efi_setup_5level_paging(void) { return EFI_SUCCESS; }
|
|
static inline void efi_5level_switch(void) {}
|
|
#endif
|