[<prev] [next>] [day] [month] [year] [list]
Message-Id: <20201215000232.25594-1-rdunlap@infradead.org>
Date: Mon, 14 Dec 2020 16:02:32 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: linux-kernel@...r.kernel.org
Cc: Randy Dunlap <rdunlap@...radead.org>, x86@...nel.org,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>
Subject: [PATCH -next] x86: vmlinux.lds.S: explain link error better when PHYSICAL_START is LARGE
On i386, when CONFIG_PHYSICAL_START is very large, it causes a
confusing or misleading linker error message:
ld: kernel image bigger than KERNEL_IMAGE_SIZE
so expand this message to include the possibility that the problem
could be due to CONFIG_PHYSICAL_START.
Signed-off-by: Randy Dunlap <rdunlap@...radead.org>
Cc: x86@...nel.org
Cc: Thomas Gleixner <tglx@...utronix.de>
Cc: Ingo Molnar <mingo@...hat.com>
Cc: Borislav Petkov <bp@...en8.de>
Cc: "H. Peter Anvin" <hpa@...or.com>
---
arch/x86/kernel/vmlinux.lds.S | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20201214.orig/arch/x86/kernel/vmlinux.lds.S
+++ linux-next-20201214/arch/x86/kernel/vmlinux.lds.S
@@ -458,7 +458,7 @@ SECTIONS
* The ASSERT() sink to . is intentional, for binutils 2.14 compatibility:
*/
. = ASSERT((_end - LOAD_OFFSET <= KERNEL_IMAGE_SIZE),
- "kernel image bigger than KERNEL_IMAGE_SIZE");
+ "kernel image bigger than KERNEL_IMAGE_SIZE or CONFIG_PHYSICAL_START too large");
#ifdef CONFIG_X86_64
/*
Powered by blists - more mailing lists