public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Sang <oliver.sang@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kernel test robot <lkp@intel.com>,
	Oleg Nesterov <oleg@redhat.com>, <oe-kbuild-all@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: Re: include/linux/seqlock.h:1257:undefined reference to `__scoped_seqlock_bug'
Date: Fri, 5 Dec 2025 11:34:28 +0800	[thread overview]
Message-ID: <aTJSxJKhgz8KzziB@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20251204110504.GI2528459@noisy.programming.kicks-ass.net>

hi, Peter Zijlstra,

On Thu, Dec 04, 2025 at 12:05:04PM +0100, Peter Zijlstra wrote:
> On Wed, Dec 03, 2025 at 10:22:28PM +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:   3f9f0252130e7dd60d41be0802bf58f6471c691d
> > commit: 488f48b32654dc6be04d9cc12f75ce030c9cb21b seqlock: Change thread_group_cputime() to use scoped_seqlock_read()
> > date:   6 weeks ago
> > config: arm-mvebu_v5_defconfig (https://download.01.org/0day-ci/archive/20251203/202512032230.5pqkcg8x-lkp@intel.com/config)
> > compiler: arm-linux-gnueabi-gcc (GCC) 15.1.0
> 
> >    arm-linux-gnueabi-ld: kernel/sched/build_policy.o: in function `__scoped_seqlock_next':
> > >> include/linux/seqlock.h:1257:(.text+0x96a0): undefined reference to `__scoped_seqlock_bug'
> 
> I cannot reproduce using the gcc-15.1 toolchain from kernel.org
> 
> $ make O=tmp-build/ ARCH=arm CROSS_COMPILE=/opt/cross-15.1/bin/arm-linux-gnueabi- -j64
> 
> completes using your .config. I've tried twice now. In any case, if this
> reliably fails for you, could you try:

yes, we can reproduce reliably with the reproducer.

and yes, the issue can be fixed by below patch. thanks

Tested-by: kernel test robot <oliver.sang@intel.com>

> 
>   https://lkml.kernel.org/r/20251204104332.GG2528459@noisy.programming.kicks-ass.net
> 
> perhaps it is that same problem. If not, could you perhaps hand me the
> kernel/sched/build_policy.s file?
> 

  reply	other threads:[~2025-12-05  3:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-03 14:22 include/linux/seqlock.h:1257:undefined reference to `__scoped_seqlock_bug' kernel test robot
2025-12-04  8:19 ` Peter Zijlstra
2025-12-04 11:05 ` Peter Zijlstra
2025-12-05  3:34   ` Oliver Sang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-01-29  1:32 kernel test robot
2026-01-29  9:39 ` Peter Zijlstra
2026-01-29 10:26   ` Uros Bizjak
2026-02-19 15:39 kernel test robot
2026-04-21  4:44 kernel test robot

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=aTJSxJKhgz8KzziB@xsang-OptiPlex-9020 \
    --to=oliver.sang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --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