From: "Arnd Bergmann" <arnd@arndb.de>
To: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
"open list" <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
"Linux Regressions" <regressions@lists.linux.dev>
Cc: "Dan Carpenter" <dan.carpenter@linaro.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Peter Zijlstra" <peterz@infradead.org>
Subject: Re: next-20240712: task_work.c:(.text+0xc2): undefined reference to `irq_work_queue'
Date: Fri, 12 Jul 2024 14:28:38 +0200 [thread overview]
Message-ID: <e25a690e-6cb9-4e00-ac1d-07cda43b12de@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYv0xfJbt=+STRDu65G-Tq_w9wEH3C0q1ucyoAa7DbWLAQ@mail.gmail.com>
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@linaro.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
next prev parent reply other threads:[~2024-07-12 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 12:13 Naresh Kamboju
2024-07-12 12:28 ` Arnd Bergmann [this message]
2024-07-12 13:24 ` Peter Zijlstra
2024-07-12 14:11 ` Arnd Bergmann
2024-07-12 15:03 ` Peter Zijlstra
2024-07-18 16:25 ` Nathan Chancellor
2024-07-19 14:17 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e25a690e-6cb9-4e00-ac1d-07cda43b12de@app.fastmail.com \
--to=arnd@arndb.de \
--cc=anders.roxell@linaro.org \
--cc=bigeasy@linutronix.de \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®