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.17a 8/36] ERROR: "tick_nohz_full_running" [kernel/rcu/rcutorture.ko] undefined!
Date: Wed, 21 Aug 2019 08:57:41 -0700 [thread overview]
Message-ID: <20190821155741.GJ28441@linux.ibm.com> (raw)
In-Reply-To: <201908211316.oVkozRDj%lkp@intel.com>
On Wed, Aug 21, 2019 at 01:14:18PM +0800, kbuild test robot wrote:
> Hi Paul,
>
> FYI, the error/warning still remains.
Right you are! I have two bugs:
1. I forgot to move 8f5a099b19cf ("time: Export tick start/stop
functions for rcutorture") to precede dd891e13181a ("rcutorture:
Force on tick for readers and callback flooders").
2. I forgot to export tick_nohz_full_running.
Updating with attribution, thank you!
Thanx, Paul
> tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2019.08.17a
> head: 9120323ada960bc9f1427e546772a983ad036b9a
> commit: 14569aa16daa1cd7610624a500ed2750fe341351 [8/36] rcutorture: Force on tick for readers and callback flooders
> config: x86_64-rhel (attached as .config)
> compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
> reproduce:
> git checkout 14569aa16daa1cd7610624a500ed2750fe341351
> # 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_dep_clear_task" [kernel/rcu/rcutorture.ko] undefined!
> ERROR: "tick_nohz_dep_set_task" [kernel/rcu/rcutorture.ko] undefined!
> >> ERROR: "tick_nohz_full_running" [kernel/rcu/rcutorture.ko] undefined!
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
prev parent reply other threads:[~2019-08-21 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 5:14 kbuild test robot
2019-08-21 15:57 ` 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=20190821155741.GJ28441@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome