From: "Arnd Bergmann" <arnd@arndb.de>
To: "Heiko Carstens" <hca@linux.ibm.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>, "Will Deacon" <will@kernel.org>,
"Boqun Feng" <boqun@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH] seqlock: Allow UBSAN_ALIGNMENT to fail optimizing
Date: Tue, 19 May 2026 13:30:38 +0200 [thread overview]
Message-ID: <96b8ee68-a6e7-4496-8510-14812d9a38ec@app.fastmail.com> (raw)
In-Reply-To: <20260519110315.1385307-1-hca@linux.ibm.com>
On Tue, May 19, 2026, at 13:03, Heiko Carstens wrote:
> With gcc-15 and gcc-16 with UBSAN_ALIGNMENT enabled the compiler fails to
> inline and optimize __scoped_seqlock_bug() away on s390:
technically
s/on s390//
since I have been able to reproduce the problem across architectures
now.
> s390x-16.1.0-ld: kernel/sched/build_policy.o: in function
> `__scoped_seqlock_next':
> /.../seqlock.h:1286:(.text+0x22030): undefined reference to
> `__scoped_seqlock_bug'
>
> Fix this by adding UBSAN_ALIGNMENT to the list of config options where a
> not inlined empty __scoped_seqlock_bug() is allowed.
>
> Reported-by: Arnd Bergmann <arnd@arndb.de>
> Closes: https://lore.kernel.org/r/20260515092057.810542-1-arnd@kernel.org/
> Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
I was about to send the same patch.
Tested-by: Arnd Bergmann <arnd@arndb.de>
Arnd
next prev parent reply other threads:[~2026-05-19 11:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 11:03 Heiko Carstens
2026-05-19 11:30 ` Arnd Bergmann [this message]
2026-05-20 8:28 ` [tip: locking/core] " tip-bot2 for Heiko Carstens
2026-05-28 10:30 ` tip-bot2 for Heiko Carstens
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=96b8ee68-a6e7-4496-8510-14812d9a38ec@app.fastmail.com \
--to=arnd@arndb.de \
--cc=boqun@kernel.org \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®