mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
	open list <linux-kernel@vger.kernel.org>,
	lkft-triage@lists.linaro.org,
	Linux Regressions <regressions@lists.linux.dev>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Anders Roxell <anders.roxell@linaro.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: next-20240712: task_work.c:(.text+0xc2): undefined reference to `irq_work_queue'
Date: Fri, 12 Jul 2024 15:24:27 +0200	[thread overview]
Message-ID: <20240712132427.GJ27299@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <e25a690e-6cb9-4e00-ac1d-07cda43b12de@app.fastmail.com>

On Fri, Jul 12, 2024 at 02:28:38PM +0200, Arnd Bergmann wrote:
> 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

Thanks, that initial report was mostly useless without that sha. I do
wonder why 0day build robot didn't complain to me about this. It seems
something it should definitely find.

> 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.

ARM seems to have HAVE_NMI while also being one of the architectures
that is now failing.

I'm a bit confused though, perf is already depending on irq_work (and
perf is the user of TWA_NMI_CURRENT). So I'm not exactly sure what
config fail is leading to all this.

I suppose we can do something like the below.. it'll end up in a runtime
fail for whoever manages to use TWA_NMI_CURRENT without also having
irq_work enabled, but that should currently be nobody.

---
 kernel/task_work.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/kernel/task_work.c b/kernel/task_work.c
index 5c2daa7ad3f9..276e245b7e7e 100644
--- a/kernel/task_work.c
+++ b/kernel/task_work.c
@@ -81,9 +81,11 @@ int task_work_add(struct task_struct *task, struct callback_head *work,
 	case TWA_SIGNAL_NO_IPI:
 		__set_notify_signal(task);
 		break;
+#ifdef CONFIG_IRQ_WORK
 	case TWA_NMI_CURRENT:
 		irq_work_queue(this_cpu_ptr(&irq_work_NMI_resume));
 		break;
+#endif
 	default:
 		WARN_ON_ONCE(1);
 		break;

  reply	other threads:[~2024-07-12 13:24 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
2024-07-12 13:24   ` Peter Zijlstra [this message]
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=20240712132427.GJ27299@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --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=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®