[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87plddh4wl.ffs@tglx>
Date: Sat, 02 Aug 2025 21:58:34 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: kernel test robot <lkp@...el.com>
Cc: oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [tip:x86/urgent 2/2] irq.c:undefined reference to
`lock_vector_lock'
On Sat, Aug 02 2025 at 20:02, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
> head: 69adc077da4c247dd39a8a0e3a898a25924e98d0
> commit: 69adc077da4c247dd39a8a0e3a898a25924e98d0 [2/2] x86/irq: Plug vector setup race
> config: i386-buildonly-randconfig-2002-20250802 (https://download.01.org/0day-ci/archive/20250802/202508022015.ZX6l8pZr-lkp@intel.com/config)
> compiler: gcc-12 (Debian 12.2.0-14+deb12u1) 12.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250802/202508022015.ZX6l8pZr-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@...el.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202508022015.ZX6l8pZr-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> ld: arch/x86/kernel/irq.o: in function `__common_interrupt':
>>> irq.c:(.text+0x4f): undefined reference to `lock_vector_lock'
>>> ld: irq.c:(.text+0x73): undefined reference to `unlock_vector_lock'
> ld: irq.c:(.text+0xa8): undefined reference to `unlock_vector_lock'
> ld: irq.c:(.text+0xc5): undefined reference to `unlock_vector_lock'
Bah. The config guard in hw_irq.h is bogus. It's equally bogus as the
whole APIC=n legacy which we still carry around for no good reason.
I've amended the commit and force pushed the branch...
Powered by blists - more mailing lists