From: Vincent Donnefort <vdonnefort@google.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: trace/simple_ring_buffer build failure on parisc, sparc64
Date: Wed, 23 Sep 2026 08:19:08 +0100 [thread overview]
Message-ID: <arN9bPXyZFt0DV3H@google.com> (raw)
In-Reply-To: <5574c9e6-9ed2-4ee6-a2b2-fb6ee81e83a1@roeck-us.net>
On Tue, Sep 22, 2026 at 08:57:05AM -0700, Guenter Roeck wrote:
> Hi,
>
> when trying to build parisc:allmodconfig or sparc64:allmodconfig,
> I get the following errors.
>
> Building parisc:allmodconfig ... failed
> --------------
> Error log:
> Unexpected symbols in kernel/trace/simple_ring_buffer.o:
> U __atomic_hash
> U trace_hardirqs_off
> U trace_hardirqs_on
> U warn_bogus_irq_restore
>
> Building sparc64:allmodconfig ... failed
> --------------
> Error log:
> Unexpected symbols in kernel/trace/simple_ring_buffer.o:
> U
> U
> U current_thread_info_reg
Thanks for the report. I could reproduce with clang. I should have a fix
shortly.
>
> I always thought this has to do with my environment and/or C compiler, but
> it seems as if the problem appears to be generic.
>
> I have no idea what causes the problem, why only those architectures are
> affected, or how to fix it. If anyone has an idea, please let me know and
> I'll be happy to write a patch and/or test it.
>
> I disabled CONFIG_RING_BUFFER for test builds of parisc and sparc64 for
> now, so this does not directly affect my test builds anymore. This is
> primarily a report that the problem exists, not a request to fix it.
>
> Thanks,
> Guenter
--
Vincent
next prev parent reply other threads:[~2026-09-23 7:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 15:57 trace/simple_ring_buffer build failure on parisc, sparc64 Guenter Roeck
2026-09-23 7:19 ` Vincent Donnefort [this message]
2026-09-23 7:44 ` Vincent Donnefort
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=arN9bPXyZFt0DV3H@google.com \
--to=vdonnefort@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.