lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Date:   Mon, 14 Dec 2020 16:02:32 -0800
From:   Randy Dunlap <>
Cc:     Randy Dunlap <>,,
        Thomas Gleixner <>,
        Ingo Molnar <>, Borislav Petkov <>,
        "H. Peter Anvin" <>
Subject: [PATCH -next] x86: 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 <>
Cc: Thomas Gleixner <>
Cc: Ingo Molnar <>
Cc: Borislav Petkov <>
Cc: "H. Peter Anvin" <>
 arch/x86/kernel/ |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-next-20201214.orig/arch/x86/kernel/
+++ linux-next-20201214/arch/x86/kernel/
@@ -458,7 +458,7 @@ SECTIONS
  * The ASSERT() sink to . is intentional, for binutils 2.14 compatibility:
-	   "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