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.07.31a 122/123] ERROR: "tick_nohz_dep_set_task" [kernel/rcu/rcutorture.ko] undefined!
Date: Wed, 7 Aug 2019 15:38:09 -0700 [thread overview]
Message-ID: <20190807223809.GJ28441@linux.ibm.com> (raw)
In-Reply-To: <201908080655.i4dbZSUm%lkp@intel.com>
On Thu, Aug 08, 2019 at 06:06:58AM +0800, kbuild test robot wrote:
> tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2019.07.31a
> head: 71cf692f482ff45802352cf85a8880035fca9e52
> commit: 1e900d78f345ee808992b1212c0388a5c8381b96 [122/123] rcutorture: Force on tick for readers and callback flooders
> config: x86_64-randconfig-h001-201930 (attached as .config)
> compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
> reproduce:
> git checkout 1e900d78f345ee808992b1212c0388a5c8381b96
> # 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_set_task" [kernel/rcu/rcutorture.ko] undefined!
> >> ERROR: "tick_nohz_dep_clear_task" [kernel/rcu/rcutorture.ko] undefined!
> >> ERROR: "tick_nohz_full_running" [kernel/rcu/rcutorture.ko] undefined!
This commit has been fixed by bb72f77a5503 ("rcutorture: Force on tick
for readers and callback flooders"), which no longer invokes these
three functions.
Thanx, Paul
prev parent reply other threads:[~2019-08-07 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 22:06 [rcu:dev.2019.07.31a 122/123] ERROR: "tick_nohz_dep_set_task" [kernel/rcu/rcutorture.ko] undefined! kbuild test robot
2019-08-07 22:38 ` 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=20190807223809.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 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.