x86: Disable image size check for test builds
PATCH v4 1/1 x86: Disable image size check for test builds
64-bit allyesconfig builds fail with
x86_64-linux-ld: kernel image bigger than KERNEL_IMAGE_SIZE
Bisect points to commit 6f110a5e4f99 ("Disable SLUB_TINY for build testing") as the responsible commit. Reverting that patch does indeed fix the problem. Further analysis shows that disabling SLUB_TINY enables KASAN, and that KASAN is responsible for the image size increase.
Solve the build problem by disabling the image size check for test builds.
While at it, fix typo in associated comment (sink -> sync).
---
v4: Added comment explaining the change
Fixed sink -> sync comment
(both thanks to Andrew).
v3: Disabled image size check instead of disabling KASAN
Updated subject to match change
Updated Cc: list to reflect affected maintainers
v2: Disabled KASAN unconditionally for test builds
Link: https://lore.kernel.org/lkml/[email protected]/
Link to RFC:
https://lore.kernel.org/lkml/[email protected]/
arch/x86/kernel/vmlinux.lds.S | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-)
arch/x86/kernel/vmlinux.lds.S +9 -1
@@ -466,10 +466,18 @@ SECTIONS } /* - * The ASSERT() sink to . is intentional, for binutils 2.14 compatibility: + * COMPILE_TEST kernels can be large - CONFIG_KASAN, for example, can cause + * this. Let's assume that nobody will be running a COMPILE_TEST kernel and + * let's assert that fuller build coverage is more valuable than being able to + * run a COMPILE_TEST kernel. + */ +#ifndef CONFIG_COMPILE_TEST +/* + * The ASSERT() sync to . is intentional, for binutils 2.14 compatibility: */ . = ASSERT((_end - LOAD_OFFSET <= KERNEL_IMAGE_SIZE), "kernel image bigger than KERNEL_IMAGE_SIZE"); +#endif /* needed for Clang - see arch/x86/entry/entry.S */ PROVIDE(__ref_stack_chk_guard = __stack_chk_guard);
Signature · 1 line
2.45.2
Quoted 2 lines · Guenter Roeck
Solve the build problem by disabling the image size check for test builds.
What _actually_ breaks when this assertion is in play? I assume upon decompression that the kernel image overflows into the fixmap area and then the fun begins.
Does anything useful come out of the kernel or is it just a fabulous crash?
Because COMPILE_TEST sounds pretty benign:
Quoted 3 lines
If you are a developer and want to build everything available, say Y here. If you are a user/distributor, say N here to exclude useless drivers to be distributed.
at the *LEAST* if we are going to go down this road, can we make the help text more scary and tell users that they might end up with an unbootable kernel?