From: Salvatore Bonaccorso <carnil@debian.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@kernel.org, oleg@redhat.com, linux-kernel@vger.kernel.org,
debian-kernel@lists.debian.org, Kees Cook <kees@debian.org>
Subject: Re: [PATCH] seqlock: Allow UBSAN to fail optimizing
Date: Sat, 31 Jan 2026 10:39:42 +0100 [thread overview]
Message-ID: <aX3N3jgLEJ-jHlQi@eldamar.lan> (raw)
In-Reply-To: <20260129110733.GA166857@noisy.programming.kicks-ass.net>
Hi Peter,
[Adding Kees as well]
On Thu, Jan 29, 2026 at 12:07:33PM +0100, Peter Zijlstra wrote:
>
> Very similar to commit:
>
> b94d45b6bbb4 ("seqlock: Allow KASAN to fail optimizing")
>
> mark UBSAN as failing to optimize and not suitable for release builds.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202601290910.uwScjRjc-lkp@intel.com/
> Link: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123873
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
>
> Debian folks, can you please remove CONFIG_UBSAN=y from your builds,
> this is, per GCC devs, not a feature suitable for production!
>
> diff --git a/include/linux/seqlock.h b/include/linux/seqlock.h
> index c00063dffba3..436f05bf5dd7 100644
> --- a/include/linux/seqlock.h
> +++ b/include/linux/seqlock.h
> @@ -1259,14 +1259,14 @@ static __always_inline void __scoped_seqlock_cleanup(struct ss_tmp *sst)
>
> extern void __scoped_seqlock_invalid_target(void);
>
> -#if (defined(CONFIG_CC_IS_GCC) && CONFIG_GCC_VERSION < 90000) || defined(CONFIG_KASAN)
> +#if (defined(CONFIG_CC_IS_GCC) && CONFIG_GCC_VERSION < 90000) || defined(CONFIG_KASAN) || defined(CONFIG_UBSAN)
> /*
> * For some reason some GCC-8 architectures (nios2, alpha) have trouble
> * determining that the ss_done state is impossible in __scoped_seqlock_next()
> * below.
> *
> - * Similarly KASAN is known to confuse compilers enough to break this. But we
> - * don't care about code quality for KASAN builds anyway.
> + * Similarly *SAN is known to confuse compilers enough to break this. But we
> + * don't care about code quality for *SAN builds anyway.
> */
> static inline void __scoped_seqlock_bug(void) { }
> #else
Kees, Peter approached the Debian kernel list above to drop
CONFIG_UBSAN again, which, so I think we need to revert your
6cfadabfe015 ("Enable UBSAN_BOUNDS and UBSAN_SHIFT"):
https://salsa.debian.org/kernel-team/linux/-/commit/6cfadabfe015fa0d659fc8e3efd495cbcae3e44e
I have make a MR for our packaging for the change in
https://salsa.debian.org/kernel-team/linux/-/merge_requests/1804
Regards,
Salvatore
next prev parent reply other threads:[~2026-01-31 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 11:07 Peter Zijlstra
2026-01-31 9:39 ` Salvatore Bonaccorso [this message]
2026-01-31 18:42 ` Kees Cook
2026-02-01 11:47 ` Peter Zijlstra
2026-02-02 3:39 ` Kees Cook
2026-02-02 8:29 ` Peter Zijlstra
2026-02-02 16:01 ` Kees Cook
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=aX3N3jgLEJ-jHlQi@eldamar.lan \
--to=carnil@debian.org \
--cc=debian-kernel@lists.debian.org \
--cc=kees@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.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
Powered by JetHome