x86/corruption-check: Remove the BIOS memory corruption check feature
Subsystems (3)
PATCH v3 1/1 x86/corruption-check: Remove the BIOS memory corruption check feature
By default, the BIOS memory corruption check works by reserving the first 64 KiB physical area from memblock, zeroing it and then scanning it periodically.
However, this functionality has been broken in its default configuration since v5.13 by two commits:
- Commit a799c2bd29d1 ("x86/setup: Consolidate early memory reservations"). Moved trim_low_memory_range() into early_reserve_memory(), which runs earlier in setup_arch(), causing the first 64 KiB to be reserved (when CONFIG_X86_RESERVE_LOW=64) before setup_bios_corruption_check() runs
- Commit f1d4d47c5851 ("x86/setup: Always reserve the first 1M of RAM"). Hardcodes the reservation of the first 64 KiB early in early_reserve_memory()
It might be possible to get the default case to work by allowing setup_bios_corruption_check() to run first, but it's just not worth it given that the kernel will never access the first 64 KiB area anyway.
Lastly, note that it's possible to get the corruption check to work with a different region by passing memory_corruption_check_size=. However, the main goal of the feature was to check the first 64 KiB. Besides, the region picked will be almost random as setup_bios_corruption_check() will pick a region by size.
---
Notes:
- Posting late in the cycle, but this is not urgent
- v2 was mangled by my MUA and did not apply, the diff is unchanged
v3
- Updated changelog to emphasize that the default configuration is broken (Thorsten)
- Improved subject prefix
- Resending on top of latest Linus tree
v2
- Rebased against latest Linus tree (v7.2-rc4)
- Improved changelog
.../admin-guide/kernel-parameters.txt | 23 --- arch/x86/Kconfig | 30 --- arch/x86/configs/i386_defconfig | 1 - arch/x86/configs/x86_64_defconfig | 1 - arch/x86/include/asm/bios_ebda.h | 17 -- arch/x86/include/asm/setup.h | 1 - arch/x86/kernel/Makefile | 2 - arch/x86/kernel/check.c | 187 ------------------ arch/x86/kernel/setup.c | 4 - 9 files changed, 266 deletions(-) delete mode 100644 arch/x86/kernel/check.c
Documentation/admin-guide/kernel-parameters.txt +0 -23
@@ -3984,29 +3984,6 @@ Kernel parameters specified as e820 types, e.g., 1 = RAM, 2 = reserved, 3 = ACPI, 12 = PRAM. - memory_corruption_check=0/1 [X86,EARLY] - Some BIOSes seem to corrupt the first 64k of - memory when doing things like suspend/resume. - Setting this option will scan the memory - looking for corruption. Enabling this will - both detect corruption and prevent the kernel - from using the memory being corrupted. - However, it's intended as a diagnostic tool; if - repeatable BIOS-originated corruption always - affects the same memory, you can use memmap= - to prevent the kernel from using that memory. - - memory_corruption_check_size=size [X86,EARLY] - By default it checks for corruption in the low - 64k, making this memory unavailable for normal - use. Use this parameter to scan for - corruption in more or less memory. - - memory_corruption_check_period=seconds [X86,EARLY] - By default it checks for corruption every 60 - seconds. Use this parameter to check at some - other rate. 0 disables periodic checking. - memory_hotplug.memmap_on_memory [KNL,X86,ARM] Boolean flag to enable this feature. Format: {on | off (default)}
arch/x86/Kconfig +0 -30
@@ -1605,36 +1605,6 @@ config X86_PMEM_LEGACY Say Y if unsure. -config X86_CHECK_BIOS_CORRUPTION - bool "Check for low memory corruption" - help - Periodically check for memory corruption in low memory, which - is suspected to be caused by BIOS. Even when enabled in the - configuration, it is disabled at runtime. Enable it by - setting "memory_corruption_check=1" on the kernel command - line. By default it scans the low 64k of memory every 60 - seconds; see the memory_corruption_check_size and - memory_corruption_check_period parameters in - Documentation/admin-guide/kernel-parameters.rst to adjust this. - - When enabled with the default parameters, this option has - almost no overhead, as it reserves a relatively small amount - of memory and scans it infrequently. It both detects corruption - and prevents it from affecting the running system. - - It is, however, intended as a diagnostic tool; if repeatable - BIOS-originated corruption always affects the same memory, - you can use memmap= to prevent the kernel from using that - memory. - -config X86_BOOTPARAM_MEMORY_CORRUPTION_CHECK - bool "Set the default setting of memory_corruption_check" - depends on X86_CHECK_BIOS_CORRUPTION - default y - help - Set whether the default state of memory_corruption_check is - on or off. - config MTRR def_bool y prompt "MTRR (Memory Type Range Register) support" if EXPERT
arch/x86/configs/i386_defconfig +0 -1
@@ -36,7 +36,6 @@ CONFIG_PARAVIRT=y CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y CONFIG_X86_MSR=y CONFIG_X86_CPUID=y -CONFIG_X86_CHECK_BIOS_CORRUPTION=y # CONFIG_MTRR_SANITIZER is not set CONFIG_EFI=y CONFIG_EFI_STUB=y
arch/x86/configs/x86_64_defconfig +0 -1
@@ -35,7 +35,6 @@ CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y CONFIG_X86_MSR=y CONFIG_X86_CPUID=y CONFIG_NUMA=y -CONFIG_X86_CHECK_BIOS_CORRUPTION=y # CONFIG_MTRR_SANITIZER is not set CONFIG_EFI=y CONFIG_EFI_STUB=y
arch/x86/include/asm/bios_ebda.h +0 -17
@@ -20,21 +20,4 @@ static inline unsigned int get_bios_ebda(void)void reserve_bios_regions (void ); -#ifdef CONFIG_X86_CHECK_BIOS_CORRUPTION -/* -* This is obviously not a great place for this, but we want to be -* able to scatter it around anywhere in the kernel. -*/ -void check_for_bios_corruption (void ); -void start_periodic_check_for_corruption (void ); -#else -static inline void check_for_bios_corruption (void ) -{ -} - -static inline void start_periodic_check_for_corruption (void ) -{ -} -#endif -#endif /* _ASM_X86_BIOS_EBDA_H */
arch/x86/include/asm/setup.h +0 -1
@@ -42,7 +42,6 @@ static inline void vsmp_init(void) { }struct pt_regs ; -void setup_bios_corruption_check (void );void early_platform_quirks (void );extern unsigned long saved_video_mode;
arch/x86/kernel/Makefile +0 -2
@@ -149,8 +149,6 @@ obj-$(CONFIG_JAILHOUSE_GUEST) += jailhouse.o obj-$(CONFIG_EISA) += eisa.o obj-$(CONFIG_PCSPKR_PLATFORM) += pcspeaker.o -obj-$(CONFIG_X86_CHECK_BIOS_CORRUPTION) += check.o - obj-$(CONFIG_OF) += devicetree.o obj-$(CONFIG_UPROBES) += uprobes.o
arch/x86/kernel/check.c deleted +0 -187
187 lines not on this page · raw message
arch/x86/kernel/setup.c +0 -4
@@ -1108,10 +1108,6 @@ void __init setup_arch(char **cmdline_p)/* preallocate 4k for mptable mpc */ e820__memblock_alloc_reserved_mpc_new (); -#ifdef CONFIG_X86_CHECK_BIOS_CORRUPTION -setup_bios_corruption_check (); -#endif -#ifdef CONFIG_X86_32 printk (KERN_DEBUG "initial memory mapped: [mem 0x00000000-%#010lx]\n" , (max_pfn_mapped<<PAGE_SHIFT ) -1 );
Signature · 1 line
2.55.0
Borislav Petkov
maintainerQuoted 20 lines · Luiz Capitulino
By default, the BIOS memory corruption check works by reserving the first 64 KiB physical area from memblock, zeroing it and then scanning it periodically.
However, this functionality has been broken in its default configuration since v5.13 by two commits:
- Commit
a799c2bd29d1("x86/setup: Consolidate early memory reservations"). Movedtrim_low_memory_range()intoearly_reserve_memory(), which runs earlier insetup_arch(), causing the first 64 KiB to be reserved (whenCONFIG_X86_RESERVE_LOW=64) beforesetup_bios_corruption_check()runs- Commit
f1d4d47c5851("x86/setup: Always reserve the first 1M of RAM"). Hardcodes the reservation of the first 64 KiB early inearly_reserve_memory()It might be possible to get the default case to work by allowing
setup_bios_corruption_check()to run first, but it's just not worth it given that the kernel will never access the first 64 KiB area anyway.
Quoted 5 lines
Lastly, note that it's possible to get the corruption check to work with a different region by passing memory_corruption_check_size=. However, the main goal of the feature was to check the first 64 KiB. Besides, the region picked will be almost random as
setup_bios_corruption_check()will pick a region by size.
And?
Do I want this or should it be fixed or the first 64K are not worth it to check or...?
That whole "rationale" is not really clear to me. Yes, it is broken, apparently. So let's remove it but we might get it work still... So which is it and why?
Signature · 4 lines
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquetteQuoted 27 lines · Borislav Petkov
Quoted 20 lines · Luiz Capitulino
By default, the BIOS memory corruption check works by reserving the first 64 KiB physical area from memblock, zeroing it and then scanning it periodically.
However, this functionality has been broken in its default configuration since v5.13 by two commits:
- Commit
a799c2bd29d1("x86/setup: Consolidate early memory reservations"). Movedtrim_low_memory_range()intoearly_reserve_memory(), which runs earlier insetup_arch(), causing the first 64 KiB to be reserved (whenCONFIG_X86_RESERVE_LOW=64) beforesetup_bios_corruption_check()runs- Commit
f1d4d47c5851("x86/setup: Always reserve the first 1M of RAM"). Hardcodes the reservation of the first 64 KiB early inearly_reserve_memory()It might be possible to get the default case to work by allowing
setup_bios_corruption_check()to run first, but it's just not worth it given that the kernel will never access the first 64 KiB area anyway.Quoted 5 lines
Lastly, note that it's possible to get the corruption check to work with a different region by passing memory_corruption_check_size=. However, the main goal of the feature was to check the first 64 KiB. Besides, the region picked will be almost random as
setup_bios_corruption_check()will pick a region by size.
Quoted 8 lines
And?
Do I want this or should it be fixed or the first 64K are not worth it to check or...?
That whole "rationale" is not really clear to me. Yes, it is broken, apparently. So let's remove it but we might get it work still... So which is it and why?
Right, the changelog got convoluted because I tried to document all the options. Just to make it clear: I don't think it's worth fixing this, so I'm proposing to remove it.
Here's a rewritten changelog, if you think this is good I'll send v4.
"""
x86/corruption-check: Remove the BIOS memory corruption check feature
By default, the BIOS memory corruption check works by reserving the first 64 KiB physical area from memblock, zeroing it and then scanning it periodically.
However, in its default configuration it has been broken since v5.13 by two commits:
- Commit a799c2bd29d1 ("x86/setup: Consolidate early memory reservations"). Moved trim_low_memory_range() into early_reserve_memory(), which runs earlier in setup_arch(), causing the first 64 KiB to be reserved before setup_bios_corruption_check() runs
- Commit f1d4d47c5851 ("x86/setup: Always reserve the first 1M of RAM"). Hardcodes the reservation of the first 64 KiB early in early_reserve_memory()
This has been broken for years and nobody reported it, which suggests the feature might have no users.
It may be possible to fix this by running setup_bios_corruption_check() earlier, but that's not worth doing: the feature was intended to detect corruption in the first 64 KiB but the kernel will never access that range anyway.
Note that one case still "works", which is passing memory_corruption_check_size= to scan a larger region. But this is not useful either: the parameter takes a size, not an address range, so what gets scanned is whatever memblock happens to have free below that size.
Remove the feature.
"""
H. Peter Anvin
reviewerQuoted 27 lines · Borislav Petkov
Quoted 20 lines · Luiz Capitulino
By default, the BIOS memory corruption check works by reserving the first 64 KiB physical area from memblock, zeroing it and then scanning it periodically.
However, this functionality has been broken in its default configuration since v5.13 by two commits:
- Commit
a799c2bd29d1("x86/setup: Consolidate early memory reservations"). Movedtrim_low_memory_range()intoearly_reserve_memory(), which runs earlier insetup_arch(), causing the first 64 KiB to be reserved (whenCONFIG_X86_RESERVE_LOW=64) beforesetup_bios_corruption_check()runs- Commit
f1d4d47c5851("x86/setup: Always reserve the first 1M of RAM"). Hardcodes the reservation of the first 64 KiB early inearly_reserve_memory()It might be possible to get the default case to work by allowing
setup_bios_corruption_check()to run first, but it's just not worth it given that the kernel will never access the first 64 KiB area anyway.Quoted 5 lines
Lastly, note that it's possible to get the corruption check to work with a different region by passing memory_corruption_check_size=. However, the main goal of the feature was to check the first 64 KiB. Besides, the region picked will be almost random as
setup_bios_corruption_check()will pick a region by size.
Quoted 9 lines
And?
Do I want this or should it be fixed or the first 64K are not worth it to check or...?
That whole "rationale" is not really clear to me. Yes, it is broken, apparently. So let's remove it but we might get it work still... So which is it and why?
We aren't using that memory, so there is no point spending the time scanning it periodically.