[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <e25a690e-6cb9-4e00-ac1d-07cda43b12de@app.fastmail.com>
Date: Fri, 12 Jul 2024 14:28:38 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Naresh Kamboju" <naresh.kamboju@...aro.org>,
"open list" <linux-kernel@...r.kernel.org>, lkft-triage@...ts.linaro.org,
"Linux Regressions" <regressions@...ts.linux.dev>
Cc: "Dan Carpenter" <dan.carpenter@...aro.org>,
"Anders Roxell" <anders.roxell@...aro.org>,
"Sebastian Andrzej Siewior" <bigeasy@...utronix.de>,
"Peter Zijlstra" <peterz@...radead.org>
Subject: Re: next-20240712: task_work.c:(.text+0xc2): undefined reference to
`irq_work_queue'
On Fri, Jul 12, 2024, at 14:13, Naresh Kamboju wrote:
> The 32-bit arm, mips and powerpc the tinyconfig builds failed on today's
> Linux next-20240712 tag with gcc and clang builds.
> The defconfig builds pass.
>
> GOOD: next-20240711
> BAD: next-20240712
>
> Build error:
> ------
> arm-linux-gnueabihf-ld: kernel/task_work.o: in function `task_work_add':
> task_work.c:(.text+0xc2): undefined reference to `irq_work_queue'
>
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
The call to this function was added in 466e4d801cd4 ("task_work:
Add TWA_NMI_CURRENT as an additional notify mode."). It's possible
that we may have to always enable IRQ_WORK even on non-SMP
kernels now. In practice it is already enabled in most
configurations for one reason or another, the the cost is
likely very small.
Otherwise checking for CONFIG_HAVE_NMI in the new code might work.
Arnd
Powered by blists - more mailing lists