Linux Trace Kernel
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Vincent Donnefort <vdonnefort@google.com>
Cc: "Arnd Bergmann" <arnd@kernel.org>,
	"Masami Hiramatsu" <mhiramat@kernel.org>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
	"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
	"Bill Wendling" <morbo@google.com>,
	"Justin Stitt" <justinstitt@google.com>,
	"Marc Zyngier" <maz@kernel.org>,
	"Thomas Weißschuh" <linux@weissschuh.net>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
	llvm@lists.linux.dev
Subject: Re: [PATCH] tracing: ring-buffer: allowlist clang-generated symbols
Date: Tue, 14 Jul 2026 17:56:17 -0400	[thread overview]
Message-ID: <20260714175617.319a6ec7@gandalf.local.home> (raw)
In-Reply-To: <ajKgjNuHUlteSziZ@google.com>

On Wed, 17 Jun 2026 14:26:36 +0100
Vincent Donnefort <vdonnefort@google.com> wrote:

> On Tue, Jun 16, 2026 at 06:42:03PM +0200, Arnd Bergmann wrote:
> > From: Arnd Bergmann <arnd@arndb.de>
> > 
> > In randconfig build testing using clang-22, I came across two
> > sets of extra symbols in the ring buffer code that may get
> > inserted by the compiler:
> > 
> > Unexpected symbols in kernel/trace/simple_ring_buffer.o:
> >          U memset
> > 
> > Unexpected symbols in kernel/trace/simple_ring_buffer.o:
> >                  U llvm_gcda_emit_arcs
> >                  U llvm_gcda_emit_function
> >                  U llvm_gcda_end_file
> >                  U llvm_gcda_start_file
> >                  U llvm_gcda_summary_info
> >                  U llvm_gcov_init
> > 
> > Add all of these to the allowlist.
> > 
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > ---
> >  kernel/trace/Makefile | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/kernel/trace/Makefile b/kernel/trace/Makefile
> > index f934ff586bd4..aa8564fb8ff4 100644
> > --- a/kernel/trace/Makefile
> > +++ b/kernel/trace/Makefile
> > @@ -146,6 +146,7 @@ KASAN_SANITIZE_undefsyms_base.o := y  
> 
> Would "GCOV_PROFILE_undefsyms_base.o := y" work?

Arnd?

-- Steve

> 
> >  
> >  UNDEFINED_ALLOWLIST = __asan __gcov __kasan __kcsan __hwasan __sancov __sanitizer __tsan __ubsan __msan \
> >  		      __aeabi_unwind_cpp __s390_indirect_jump __x86_indirect_thunk simple_ring_buffer \
> > +		      memset llvm_gcda llvm_gcov \
> >  		      $(shell $(NM) -u $(obj)/undefsyms_base.o 2>/dev/null | awk '{print $$2}')
> >  
> >  quiet_cmd_check_undefined = NM      $<
> > -- 
> > 2.39.5
> >   


  reply	other threads:[~2026-07-14 21:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16 16:42 [PATCH] tracing: ring-buffer: allowlist clang-generated symbols Arnd Bergmann
2026-06-17 13:26 ` Vincent Donnefort
2026-07-14 21:56   ` Steven Rostedt [this message]
2026-07-15  7:38     ` Arnd Bergmann
2026-07-15 23:40       ` 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=20260714175617.319a6ec7@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=justinstitt@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=llvm@lists.linux.dev \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=maz@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=vdonnefort@google.com \
    /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