From: Marc Zyngier <maz@kernel.org>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: "Vincent Donnefort" <vdonnefort@google.com>,
"Arnd Bergmann" <arnd@kernel.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Oliver Upton" <oupton@kernel.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] tracing: add more symbols to whitelist
Date: Thu, 12 Mar 2026 15:21:19 +0000 [thread overview]
Message-ID: <86zf4d5b0w.wl-maz@kernel.org> (raw)
In-Reply-To: <d4fa3ee4-22ed-4ba3-afa3-4fe7a22b226c@app.fastmail.com>
On Thu, 12 Mar 2026 14:37:50 +0000,
"Arnd Bergmann" <arnd@arndb.de> wrote:
>
> On Thu, Mar 12, 2026, at 14:40, Vincent Donnefort wrote:
> > On Thu, Mar 12, 2026 at 01:35:43PM +0100, Arnd Bergmann wrote:
> >> diff --git a/kernel/trace/Makefile b/kernel/trace/Makefile
>
> >> +UNDEFINED_ALLOWLIST += ftrace_likely_update __hwasan_load __hwasan_store __hwasan_tag_memory
> >> +UNDEFINED_ALLOWLIST += warn_bogus_irq_restore warn_slowpath_fmt __stack_chk_guard
>
> >
> > Thanks for the patch.
> >
> > Most of those ones are covered here
> > https://lore.kernel.org/all/20260312113535.2213350-1-vdonnefort@google.com/.
> >
> > This should fix allmodconfig.
>
> The ones I see in that patch look entirely different from the ones
> I found.
>
> > For the ones not covered, I'm working on a follow-up patch using a different
> > approach which should fix them. I'll be able to share it today or tomorrow. Not
> > sure if we want to take this temporarily?
>
> I can wait, my randconfig setup has my patch applied locally for now,
> but I've only fixed the ones I saw on three architectures with gcc-16.0.1,
> while Nathan's list seems to be mostly for clang specific symbols.
>
> A lot of them also don't show up in allmodconfig builds, only after a
> larger number of randconfig configurations.
I've decided to take this patch anyway, on top of Vincent's. Should a
more generic solution arise, I can always drop both.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-03-12 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 12:35 [PATCH 1/3] KVM: arm64: fix include path for ring buffer implementation Arnd Bergmann
2026-03-12 12:35 ` [PATCH 2/3] tracing: add more symbols to whitelist Arnd Bergmann
2026-03-12 13:40 ` Vincent Donnefort
2026-03-12 14:37 ` Arnd Bergmann
2026-03-12 15:21 ` Marc Zyngier [this message]
2026-03-12 15:37 ` Arnd Bergmann
2026-03-12 12:35 ` [PATCH 3/3] KVM: arm64: tracing: add ftrace dependency Arnd Bergmann
2026-03-12 13:52 ` Vincent Donnefort
2026-03-12 13:35 ` [PATCH 1/3] KVM: arm64: fix include path for ring buffer implementation Vincent Donnefort
2026-03-12 15:45 ` (subset) " Marc Zyngier
2026-03-12 22:08 ` Nathan Chancellor
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=86zf4d5b0w.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=oupton@kernel.org \
--cc=rostedt@goodmis.org \
--cc=vdonnefort@google.com \
--cc=will@kernel.org \
/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