From: kbuild test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: [rcu:dev.2019.08.01b 66/72] kernel/rcu/rcutorture.c:1767:4: error: implicit declaration of function 'rcu_momentary_dyntick_idle'
Date: Sat, 10 Aug 2019 04:38:18 +0800 [thread overview]
Message-ID: <201908100450.jJl7obfs%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2161 bytes --]
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2019.08.01b
head: 6c92be8b1b81158f48ab0cb00d34d451dae1fa3c
commit: 5f4264e33ca4e7cee035cee5bfa62f6d1bbf2cda [66/72] rcutorture: Emulate dyntick aspect of userspace nohz_full sojourn
config: i386-randconfig-d004-201931 (attached as .config)
compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
reproduce:
git checkout 5f4264e33ca4e7cee035cee5bfa62f6d1bbf2cda
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
kernel/rcu/rcutorture.c: In function 'rcu_torture_fwd_prog_cbfree':
>> kernel/rcu/rcutorture.c:1767:4: error: implicit declaration of function 'rcu_momentary_dyntick_idle' [-Werror=implicit-function-declaration]
rcu_momentary_dyntick_idle();
^~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/rcu_momentary_dyntick_idle +1767 kernel/rcu/rcutorture.c
1741
1742 /*
1743 * Free all callbacks on the rcu_fwd_cb_head list, either because the
1744 * test is over or because we hit an OOM event.
1745 */
1746 static unsigned long rcu_torture_fwd_prog_cbfree(void)
1747 {
1748 unsigned long flags;
1749 unsigned long freed = 0;
1750 struct rcu_fwd_cb *rfcp;
1751
1752 for (;;) {
1753 spin_lock_irqsave(&rcu_fwd_lock, flags);
1754 rfcp = rcu_fwd_cb_head;
1755 if (!rfcp) {
1756 spin_unlock_irqrestore(&rcu_fwd_lock, flags);
1757 break;
1758 }
1759 rcu_fwd_cb_head = rfcp->rfc_next;
1760 if (!rcu_fwd_cb_head)
1761 rcu_fwd_cb_tail = &rcu_fwd_cb_head;
1762 spin_unlock_irqrestore(&rcu_fwd_lock, flags);
1763 kfree(rfcp);
1764 freed++;
1765 rcu_torture_fwd_prog_cond_resched(freed);
1766 if (IS_ENABLED(CONFIG_NO_HZ_FULL))
> 1767 rcu_momentary_dyntick_idle();
1768 }
1769 return freed;
1770 }
1771
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 31261 bytes --]
reply other threads:[~2019-08-09 20:39 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=201908100450.jJl7obfs%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.ibm.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
all inboxes | Powered by JetHome®