From: kernel test robot <lkp@intel.com>
To: Sun Jian <sun.jian.kdev@gmail.com>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org
Cc: oe-kbuild-all@lists.linux.dev, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
vschneid@redhat.com, nathan@kernel.org,
nick.desaulniers+lkml@gmail.com, morbo@google.com,
justinstitt@google.com, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev, Sun Jian <sun.jian.kdev@gmail.com>
Subject: Re: [PATCH v2] sched: rcu: fix rq->{curr,donor} address space annotations
Date: Sat, 21 Feb 2026 07:19:10 +0800 [thread overview]
Message-ID: <202602210752.PVuJInZ7-lkp@intel.com> (raw)
In-Reply-To: <20260220193353.21870-1-sun.jian.kdev@gmail.com>
Hi Sun,
kernel test robot noticed the following build errors:
[auto build test ERROR on 770aaedb461a055f79b971d538678942b6607894]
url: https://github.com/intel-lab-lkp/linux/commits/Sun-Jian/sched-rcu-fix-rq-curr-donor-address-space-annotations/20260221-033739
base: 770aaedb461a055f79b971d538678942b6607894
patch link: https://lore.kernel.org/r/20260220193353.21870-1-sun.jian.kdev%40gmail.com
patch subject: [PATCH v2] sched: rcu: fix rq->{curr,donor} address space annotations
config: arc-allnoconfig (https://download.01.org/0day-ci/archive/20260221/202602210752.PVuJInZ7-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260221/202602210752.PVuJInZ7-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/202602210752.PVuJInZ7-lkp@intel.com/
All errors (new ones prefixed by >>):
arc-linux-ld: kernel/sched/core.o: in function `wake_up_if_idle':
core.c:(.text+0x1ecc): undefined reference to `lockdep_is_held'
>> arc-linux-ld: core.c:(.text+0x1ecc): undefined reference to `lockdep_is_held'
arc-linux-ld: kernel/sched/core.o: in function `__schedule':
core.c:(.sched.text+0x6a): undefined reference to `lockdep_is_held'
>> arc-linux-ld: core.c:(.sched.text+0x6a): undefined reference to `lockdep_is_held'
arc-linux-ld: core.c:(.sched.text+0x136): undefined reference to `lockdep_is_held'
arc-linux-ld: kernel/sched/core.o:core.c:(.sched.text+0x136): more undefined references to `lockdep_is_held' follow
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-20 23:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 10:20 [PATCH] sched: rcu: fix rq->{curr,donor} address space annotations Sun Jian
2026-02-14 19:44 ` kernel test robot
2026-02-20 19:33 ` [PATCH v2] " Sun Jian
2026-02-20 19:48 ` Peter Zijlstra
2026-02-21 1:53 ` sun jian
2026-02-20 23:19 ` kernel test robot [this message]
2026-02-20 23:29 ` 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=202602210752.PVuJInZ7-lkp@intel.com \
--to=lkp@intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sun.jian.kdev@gmail.com \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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