GNU/Weeb Mailing List <[email protected]>
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <[email protected]>
To: kernel test robot <[email protected]>
Cc: [email protected],
	Ammar Faizi <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>
Subject: Re: [ammarfaizi2-block:paulmck/linux-rcu/dev.2023.02.27a 108/108] kernel/rcu/rcutorture.c:3289: undefined reference to `set_nmi_torture'
Date: Tue, 7 Mar 2023 09:37:25 -0800	[thread overview]
Message-ID: <20230307173725.GK1301832@paulmck-ThinkPad-P17-Gen-1> (raw)
In-Reply-To: <[email protected]>

On Tue, Mar 07, 2023 at 01:03:43PM +0800, kernel test robot wrote:
> tree:   https://github.com/ammarfaizi2/linux-block paulmck/linux-rcu/dev.2023.02.27a
> head:   b171cbcbbd8e5f5f2e0638c5b5b5c77e3cc79007
> commit: b171cbcbbd8e5f5f2e0638c5b5b5c77e3cc79007 [108/108] rcutorture: Test NMI diagnostics
> config: arm-randconfig-r006-20230305 (https://download.01.org/0day-ci/archive/20230307/[email protected]/config)
> compiler: arm-linux-gnueabi-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/b171cbcbbd8e5f5f2e0638c5b5b5c77e3cc79007
>         git remote add ammarfaizi2-block https://github.com/ammarfaizi2/linux-block
>         git fetch --no-tags ammarfaizi2-block paulmck/linux-rcu/dev.2023.02.27a
>         git checkout b171cbcbbd8e5f5f2e0638c5b5b5c77e3cc79007
>         # 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=arm olddefconfig
>         COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash
> 
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <[email protected]>
> | Link: https://lore.kernel.org/oe-kbuild-all/[email protected]/
> 
> All errors (new ones prefixed by >>):
> 
>    arm-linux-gnueabi-ld: kernel/rcu/rcutorture.o: in function `rcutorture_test_nmis':
> >> kernel/rcu/rcutorture.c:3289: undefined reference to `set_nmi_torture'
> >> arm-linux-gnueabi-ld: kernel/rcu/rcutorture.c:3301: undefined reference to `set_nmi_torture'

This was me accidentally putting an x86-only not-for-mainline diagnostic
patch on the -rcu tree's "dev" branch.  I reset the "dev" branch to
avoid this.

							Thanx, Paul

> vim +3289 kernel/rcu/rcutorture.c
> 
>   3281	
>   3282	static void rcutorture_test_nmis(int n)
>   3283	{
>   3284	#if IS_BUILTIN(CONFIG_RCU_TORTURE_TEST)
>   3285		int cpu;
>   3286		int dumpcpu;
>   3287		int i;
>   3288	
> > 3289		set_nmi_torture(nmi_delay, nmi_halt1, nmi_halt2, nmi_halt3);
>   3290		for (i = 0; i < n; i++) {
>   3291			preempt_disable();
>   3292			cpu = smp_processor_id();
>   3293			dumpcpu = cpu + 1;
>   3294			if (dumpcpu >= nr_cpu_ids)
>   3295				dumpcpu = 0;
>   3296			pr_alert("%s: CPU %d invoking dump_cpu_task(%d)\n", __func__, cpu, dumpcpu);
>   3297			dump_cpu_task(dumpcpu);
>   3298			preempt_enable();
>   3299			schedule_timeout_uninterruptible(15 * HZ);
>   3300		}
> > 3301		set_nmi_torture(0, false, false, false);
>   3302	#else // #if IS_BUILTIN(CONFIG_RCU_TORTURE_TEST)
>   3303		WARN_ONCE(n, "Non-zero rcutorture.test_nmis=%d permitted only when rcutorture is built in.\n", test_nmis);
>   3304	#endif // #else // #if IS_BUILTIN(CONFIG_RCU_TORTURE_TEST)
>   3305	}
>   3306	
> 
> -- 
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests

      reply	other threads:[~2023-03-07 17:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  5:03 [ammarfaizi2-block:paulmck/linux-rcu/dev.2023.02.27a 108/108] kernel/rcu/rcutorture.c:3289: undefined reference to `set_nmi_torture' kernel test robot
2023-03-07 17:37 ` 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=20230307173725.GK1301832@paulmck-ThinkPad-P17-Gen-1 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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