From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: [rcu:dev.2019.08.09a 65/67] ERROR: "tick_nohz_full_running" [kernel/rcu/rcutorture.ko] undefined!
Date: Tue, 13 Aug 2019 08:49:45 -0700 [thread overview]
Message-ID: <20190813154945.GF28441@linux.ibm.com> (raw)
In-Reply-To: <201908131124.dw1rLYdU%lkp@intel.com>
On Tue, Aug 13, 2019 at 11:23:34AM +0800, kbuild test robot wrote:
> Hi Paul,
>
> First bad commit (maybe != root cause):
>
> tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2019.08.09a
> head: 8997cc705c8156fd638c6296c800ceb4f2cd4eb0
> commit: 7bcd11ce830f32631a378ff0e75836f27b202f1b [65/67] squash! idle: Prevent late-arriving interrupts from disrupting offline
> config: x86_64-rhel (attached as .config)
> compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
> reproduce:
> git checkout 7bcd11ce830f32631a378ff0e75836f27b202f1b
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> If you fix the issue, kindly add following tag
> Reported-by: kbuild test robot <lkp@intel.com>
>
> All errors (new ones prefixed by >>):
>
> >> ERROR: "tick_nohz_full_running" [kernel/rcu/rcutorture.ko] undefined!
Given that this commit did not change rcutorture or anything that
rcutorture invokes, I am having difficulty seeing how it caused
this failure. Or am I missing some indirect series of inline function
invocations?
Easy enough to add the EXPORT_SYMBOL_GPL() if it is needed! ;-)
Thanx, Paul
prev parent reply other threads:[~2019-08-13 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 3:23 [rcu:dev.2019.08.09a 65/67] ERROR: "tick_nohz_full_running" [kernel/rcu/rcutorture.ko] undefined! kbuild test robot
2019-08-13 15:49 ` 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=20190813154945.GF28441@linux.ibm.com \
--to=paulmck@linux.ibm.com \
--cc=kbuild-all@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 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.