From: kernel test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
Ammar Faizi <ammarfaizi2@gnuweeb.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>
Subject: [ammarfaizi2-block:paulmck/linux-rcu/nmitest.2023.01.20a 5/5] kernel/rcu/rcutorture.c:3291: undefined reference to `set_nmi_torture'
Date: Sat, 21 Jan 2023 13:44:42 +0800 [thread overview]
Message-ID: <202301211331.RMgsACsP-lkp@intel.com> (raw)
tree: https://github.com/ammarfaizi2/linux-block paulmck/linux-rcu/nmitest.2023.01.20a
head: 53e298568bde2c728ee2aac4ac634cca8550a4b4
commit: 53e298568bde2c728ee2aac4ac634cca8550a4b4 [5/5] rcutorture: Test NMI diagnostics
config: s390-allyesconfig (https://download.01.org/0day-ci/archive/20230121/202301211331.RMgsACsP-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 12.1.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
# https://github.com/ammarfaizi2/linux-block/commit/53e298568bde2c728ee2aac4ac634cca8550a4b4
git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
git fetch --no-tags ammarfaizi2-block paulmck/linux-rcu/nmitest.2023.01.20a
git checkout 53e298568bde2c728ee2aac4ac634cca8550a4b4
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=s390 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=s390 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
s390-linux-ld: kernel/rcu/rcutorture.o: in function `rcutorture_test_nmis':
>> kernel/rcu/rcutorture.c:3291: undefined reference to `set_nmi_torture'
>> s390-linux-ld: kernel/rcu/rcutorture.c:3303: undefined reference to `set_nmi_torture'
vim +3291 kernel/rcu/rcutorture.c
3284
3285 static void rcutorture_test_nmis(int n)
3286 {
3287 int cpu;
3288 int dumpcpu;
3289 int i;
3290
> 3291 set_nmi_torture(nmi_delay, nmi_halt1, nmi_halt2, nmi_halt3);
3292 for (i = 0; i < n; i++) {
3293 preempt_disable();
3294 cpu = smp_processor_id();
3295 dumpcpu = cpu + 1;
3296 if (dumpcpu >= nr_cpu_ids)
3297 dumpcpu = 0;
3298 pr_alert("%s: CPU %d invoking dump_cpu_task(%d)\n", __func__, cpu, dumpcpu);
3299 dump_cpu_task(dumpcpu);
3300 preempt_enable();
3301 schedule_timeout_uninterruptible(15 * HZ);
3302 }
> 3303 set_nmi_torture(0, false, false, false);
3304 }
3305
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-01-21 5:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202301211331.RMgsACsP-lkp@intel.com \
--to=lkp@intel.com \
--cc=ammarfaizi2@gnuweeb.org \
--cc=gwml@vger.gnuweeb.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paulmck@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.