[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7ee6d1aff2da6f79e08c9a3134bc8519e991f0f4.camel@infradead.org>
Date: Mon, 09 Dec 2024 15:59:55 +0000
From: David Woodhouse <dwmw2@...radead.org>
To: Borislav Petkov <bp@...en8.de>, Damien Le Moal <dlemoal@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Ingo Molnar
<mingo@...nel.org>, Thomas Gleixner <tglx@...utronix.de>, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [EXTERNAL] [PATCH] x86: Fix build regression with
CONFIG_KEXEC_JUMP enabled
On Mon, 2024-12-09 at 11:29 +0100, Borislav Petkov wrote:
> On Mon, Dec 09, 2024 at 08:53:32AM +0900, Damien Le Moal wrote:
> > Build 6.13-rc12 for x86_64 with gcc 14.2.1 fails with the error:
> >
> > ld: vmlinux.o: in function `virtual_mapped':
> > linux/arch/x86/kernel/relocate_kernel_64.S:249:(.text+0x5915b):
> > undefined reference to `saved_context_gdt_desc'
> >
> > when CONFIG_KEXEC_JUMP is enabled.
>
> Hmm, how do you trigger this? Care to share your .config?
>
> Because I can't trigger it with my gcc13 and CONFIG_KEXEC_JUMP=y
>
> It would be good to know how the 0day bot didn't catch it either...
Actually I think it did:
https://lore.kernel.org/oe-kbuild-all/202411270006.ZyyzpYf8-lkp@intel.com/
The bot had previously complained about v2 of the series, and I thought
I'd fixed it by adding the #ifdef CONFIG_KEXEC_JUMP around it. I didn't
spot that the warning linked above was actually against v3.
(In fact, *lots* of the return path from kexec is just unreachable dead
code in the case that CONFIG_KEXEC_JUMP isn't set, but it seems we're
in the habit of #ifdeffing out only the parts that actually wouldn't
compile.)
Acked-by: David Woodhouse <dwmw@...zon.co.uk>
Reported-by: kernel test robot <lkp@...el.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202411270006.ZyyzpYf8-lkp@intel.com/
Download attachment "smime.p7s" of type "application/pkcs7-signature" (5965 bytes)
Powered by blists - more mailing lists