From: "Paul E. McKenney" <paulmck@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [rcu:dev.2020.08.10a 105/111] main.c:undefined reference to `rcu_read_unlock_strict'
Date: Wed, 12 Aug 2020 13:45:48 -0700 [thread overview]
Message-ID: <20200812204548.GK4295@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <202008120752.kdAks6DZ%lkp@intel.com>
On Wed, Aug 12, 2020 at 07:39:54AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.08.10a
> head: 9dd4d242c535c30266a08806314ea6b016f94617
> commit: 9e20110f8ef2745df8f4fe2d679114dccfaaa1af [105/111] rcu: Report QS for outermost PREEMPT=n rcu_read_unlock() for strict GPs
> config: arm-mainstone_defconfig (attached as .config)
> compiler: arm-linux-gnueabi-gcc (GCC) 9.3.0
> reproduce (this is a W=1 build):
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 9e20110f8ef2745df8f4fe2d679114dccfaaa1af
> # save the attached .config to linux build tree
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arm
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> arm-linux-gnueabi-ld: init/main.o: in function `rest_init':
> >> main.c:(.ref.text+0x34): undefined reference to `rcu_read_unlock_strict'
> >> arm-linux-gnueabi-ld: main.c:(.ref.text+0x58): undefined reference to `rcu_read_unlock_strict'
Good catch, broke single-CPU yet again! ;-)
Fixed, will be merge into original with attribution.
Thanx, Paul
> arm-linux-gnueabi-ld: kernel/fork.o: in function `get_mm_exe_file':
> >> fork.c:(.text+0x3ac): undefined reference to `rcu_read_unlock_strict'
> arm-linux-gnueabi-ld: kernel/fork.o: in function `pidfd_poll':
> fork.c:(.text+0x650): undefined reference to `rcu_read_unlock_strict'
> arm-linux-gnueabi-ld: kernel/fork.o: in function `_do_fork':
> fork.c:(.text+0x2e10): undefined reference to `rcu_read_unlock_strict'
> arm-linux-gnueabi-ld: kernel/fork.o:fork.c:(.text+0x2e8c): more undefined references to `rcu_read_unlock_strict' follow
>
> ---
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
prev parent reply other threads:[~2020-08-12 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 23:39 kernel test robot
2020-08-12 20:45 ` Paul E. McKenney [this message]
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=20200812204548.GK4295@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.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
all inboxes | Powered by JetHome®