From: Peter Zijlstra <peterz@infradead.org>
To: kernel test robot <lkp@intel.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
ubizjak@gmail.com, Ingo Molnar <mingo@kernel.org>
Subject: Re: include/linux/seqlock.h:1257:undefined reference to `__scoped_seqlock_bug'
Date: Thu, 29 Jan 2026 10:39:19 +0100 [thread overview]
Message-ID: <20260129093919.GZ166857@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <202601290910.uwScjRjc-lkp@intel.com>
On Thu, Jan 29, 2026 at 09:32:00AM +0800, kernel test robot wrote:
> Hi Oleg,
>
> FYI, the error/warning still remains.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> head: 8dfce8991b95d8625d0a1d2896e42f93b9d7f68d
> commit: 488f48b32654dc6be04d9cc12f75ce030c9cb21b seqlock: Change thread_group_cputime() to use scoped_seqlock_read()
> date: 3 months ago
> config: s390-randconfig-002-20260129 (https://download.01.org/0day-ci/archive/20260129/202601290910.uwScjRjc-lkp@intel.com/config)
> compiler: s390-linux-gcc (GCC) 15.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260129/202601290910.uwScjRjc-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202601290910.uwScjRjc-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> s390-linux-ld: kernel/sched/build_policy.o: in function `__scoped_seqlock_next':
> >> include/linux/seqlock.h:1257:(.text+0x3ee04): undefined reference to `__scoped_seqlock_bug'
>
Yeah, this is an UBSAN build, and those sanitizers keep confusing
things.
The problem is, some distros seem to actually ship with that crap on
:-(.
I need to go prod some compiler folks.
Uros, do compiler folks care about optimizer quality in the face of
UBSAN or should I go kick distros for shipping with UBSAN enabled?
If s390 isn't your cup of tea, I think Ingo has a x86 config somewhere
that shows this same.
> vim +1257 include/linux/seqlock.h
>
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1251
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1252 static inline void
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1253 __scoped_seqlock_next(struct ss_tmp *sst, seqlock_t *lock, enum ss_state target)
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1254 {
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1255 switch (sst->state) {
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1256 case ss_done:
> cc39f3872c0865 Peter Zijlstra 2025-10-09 @1257 __scoped_seqlock_bug();
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1258 return;
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1259
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1260 case ss_lock:
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1261 case ss_lock_irqsave:
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1262 sst->state = ss_done;
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1263 return;
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1264
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1265 case ss_lockless:
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1266 if (!read_seqretry(lock, sst->data)) {
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1267 sst->state = ss_done;
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1268 return;
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1269 }
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1270 break;
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1271 }
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1272
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1273 switch (target) {
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1274 case ss_done:
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1275 __scoped_seqlock_invalid_target();
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1276 return;
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1277
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1278 case ss_lock:
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1279 sst->lock = &lock->lock;
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1280 spin_lock(sst->lock);
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1281 sst->state = ss_lock;
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1282 return;
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1283
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1284 case ss_lock_irqsave:
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1285 sst->lock_irqsave = &lock->lock;
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1286 spin_lock_irqsave(sst->lock_irqsave, sst->data);
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1287 sst->state = ss_lock_irqsave;
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1288 return;
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1289
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1290 case ss_lockless:
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1291 sst->data = read_seqbegin(lock);
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1292 return;
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1293 }
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1294 }
> cc39f3872c0865 Peter Zijlstra 2025-10-09 1295
>
> :::::: The code at line 1257 was first introduced by commit
> :::::: cc39f3872c0865bef992b713338df369554fa9e0 seqlock: Introduce scoped_seqlock_read()
>
> :::::: TO: Peter Zijlstra <peterz@infradead.org>
> :::::: CC: Peter Zijlstra <peterz@infradead.org>
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-01-29 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 1:32 include/linux/seqlock.h:1257:undefined reference to `__scoped_seqlock_bug' kernel test robot
2026-01-29 9:39 ` Peter Zijlstra [this message]
2026-01-29 10:26 ` Uros Bizjak
-- strict thread matches above, loose matches on Subject: below --
2026-04-21 4:44 kernel test robot
2026-02-19 15:39 kernel test robot
2025-12-03 14:22 kernel test robot
2025-12-04 8:19 ` Peter Zijlstra
2025-12-04 11:05 ` Peter Zijlstra
2025-12-05 3:34 ` Oliver Sang
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=20260129093919.GZ166857@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oleg@redhat.com \
--cc=ubizjak@gmail.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