From: kernel test robot <lkp@intel.com>
To: Florian Westphal <fw@strlen.de>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: [linux-next:master 7125/8019] net/netfilter/nfnetlink_hook.c:76:7: error: implicit declaration of function 'nft_is_active'
Date: Tue, 8 Jun 2021 21:43:50 +0800 [thread overview]
Message-ID: <202106082146.9TmnLWJk-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3059 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: ab5803bc555fe68b9b0d37b9a850d3ec601b938a
commit: e2cf17d3774c323ef6dab6e9f7c0cfc5e742afd9 [7125/8019] netfilter: add new hook nfnl subsystem
config: arc-randconfig-r031-20210608 (attached as .config)
compiler: arc-elf-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=e2cf17d3774c323ef6dab6e9f7c0cfc5e742afd9
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout e2cf17d3774c323ef6dab6e9f7c0cfc5e742afd9
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=arc
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
net/netfilter/nfnetlink_hook.c: In function 'nfnl_hook_put_nft_chain_info':
>> net/netfilter/nfnetlink_hook.c:76:7: error: implicit declaration of function 'nft_is_active' [-Werror=implicit-function-declaration]
76 | if (!nft_is_active(net, chain))
| ^~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/nft_is_active +76 net/netfilter/nfnetlink_hook.c
58
59 static int nfnl_hook_put_nft_chain_info(struct sk_buff *nlskb,
60 const struct nfnl_dump_hook_data *ctx,
61 unsigned int seq,
62 const struct nf_hook_ops *ops)
63 {
64 struct net *net = sock_net(nlskb->sk);
65 struct nlattr *nest, *nest2;
66 struct nft_chain *chain;
67 int ret = 0;
68
69 if (ops->hook_ops_type != NF_HOOK_OP_NF_TABLES)
70 return 0;
71
72 chain = ops->priv;
73 if (WARN_ON_ONCE(!chain))
74 return 0;
75
> 76 if (!nft_is_active(net, chain))
77 return 0;
78
79 nest = nla_nest_start(nlskb, NFNLA_HOOK_CHAIN_INFO);
80 if (!nest)
81 return -EMSGSIZE;
82
83 ret = nla_put_be32(nlskb, NFNLA_HOOK_INFO_TYPE,
84 htonl(NFNL_HOOK_TYPE_NFTABLES));
85 if (ret)
86 goto cancel_nest;
87
88 nest2 = nla_nest_start(nlskb, NFNLA_HOOK_INFO_DESC);
89 if (!nest2)
90 goto cancel_nest;
91
92 ret = nla_put_string(nlskb, NFTA_CHAIN_TABLE, chain->table->name);
93 if (ret)
94 goto cancel_nest;
95
96 ret = nla_put_string(nlskb, NFTA_CHAIN_NAME, chain->name);
97 if (ret)
98 goto cancel_nest;
99
100 nla_nest_end(nlskb, nest2);
101 nla_nest_end(nlskb, nest);
102 return ret;
103
104 cancel_nest:
105 nla_nest_cancel(nlskb, nest);
106 return -EMSGSIZE;
107 }
108
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 26244 bytes --]
reply other threads:[~2021-06-08 13:44 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=202106082146.9TmnLWJk-lkp@intel.com \
--to=lkp@intel.com \
--cc=fw@strlen.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=pablo@netfilter.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