From: kbuild test robot <lkp@intel.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [rcu:dev.2019.12.08a 37/105] net/tipc/crypto.c:261:39: error: implicit declaration of function 'lockdep_is_held'; did you mean 'lockdep_rtnl_is_held'?
Date: Tue, 10 Dec 2019 09:38:21 +0800 [thread overview]
Message-ID: <201912100911.1F4xx4U8%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2695 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2019.12.08a
head: 27628657c4a5dc4ed361a933fd368059d1653ac2
commit: 60a637364607f8086690fe03d31ca2f255c6e79e [37/105] rcu: Remove rcu_swap_protected()
config: c6x-allyesconfig (attached as .config)
compiler: c6x-elf-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 60a637364607f8086690fe03d31ca2f255c6e79e
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=c6x
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
net/tipc/crypto.c: In function 'tipc_crypto_key_try_align':
net/tipc/crypto.c:261:2: error: implicit declaration of function 'rcu_swap_protected'; did you mean 'rcu_sync_enter'? [-Werror=implicit-function-declaration]
rcu_swap_protected((rcu_ptr), (ptr), lockdep_is_held(lock))
^
net/tipc/crypto.c:1192:3: note: in expansion of macro 'tipc_aead_rcu_swap'
tipc_aead_rcu_swap(rx->aead[key.passive], tmp2, &rx->lock);
^~~~~~~~~~~~~~~~~~
>> net/tipc/crypto.c:261:39: error: implicit declaration of function 'lockdep_is_held'; did you mean 'lockdep_rtnl_is_held'? [-Werror=implicit-function-declaration]
rcu_swap_protected((rcu_ptr), (ptr), lockdep_is_held(lock))
^
net/tipc/crypto.c:1192:3: note: in expansion of macro 'tipc_aead_rcu_swap'
tipc_aead_rcu_swap(rx->aead[key.passive], tmp2, &rx->lock);
^~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +261 net/tipc/crypto.c
fc1b6d6de22087 Tuong Lien 2019-11-08 256
fc1b6d6de22087 Tuong Lien 2019-11-08 257 #define tipc_aead_rcu_ptr(rcu_ptr, lock) \
fc1b6d6de22087 Tuong Lien 2019-11-08 258 rcu_dereference_protected((rcu_ptr), lockdep_is_held(lock))
fc1b6d6de22087 Tuong Lien 2019-11-08 259
fc1b6d6de22087 Tuong Lien 2019-11-08 260 #define tipc_aead_rcu_swap(rcu_ptr, ptr, lock) \
fc1b6d6de22087 Tuong Lien 2019-11-08 @261 rcu_swap_protected((rcu_ptr), (ptr), lockdep_is_held(lock))
fc1b6d6de22087 Tuong Lien 2019-11-08 262
:::::: The code at line 261 was first introduced by commit
:::::: fc1b6d6de2208774efd2a20bf0daddb02d18b1e0 tipc: introduce TIPC encryption & authentication
:::::: TO: Tuong Lien <tuong.t.lien@dektech.com.au>
:::::: CC: David S. Miller <davem@davemloft.net>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 50701 bytes --]
next reply other threads:[~2019-12-10 1:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 1:38 kbuild test robot [this message]
2019-12-10 3:18 ` Paul E. McKenney
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=201912100911.1F4xx4U8%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
/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®