From: kbuild test robot <lkp@intel.com>
To: Fernando Fernandez Mancera <ffmancera@riseup.net>
Cc: kbuild-all@01.org, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org, Pablo Neira Ayuso <pablo@netfilter.org>
Subject: [nf-next:master 9/20] net/ipv6/netfilter.c:237:26: error: '__cookie_v6_init_sequence' undeclared here (not in a function); did you mean 'cookie_init_sequence'?
Date: Tue, 25 Jun 2019 03:03:41 +0800 [thread overview]
Message-ID: <201906250340.TX2hwmgK%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2383 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git master
head: dbb5281a1f84b2f93032d4864c211ce8a20811a7
commit: 3006a5224f15cf68edc4878799ac6d6089861518 [9/20] netfilter: synproxy: remove module dependency on IPv6 SYNPROXY
config: arm64-defconfig (attached as .config)
compiler: aarch64-linux-gcc (GCC) 7.4.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 3006a5224f15cf68edc4878799ac6d6089861518
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=arm64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
Note: the nf-next/master HEAD dbb5281a1f84b2f93032d4864c211ce8a20811a7 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
>> net/ipv6/netfilter.c:237:26: error: '__cookie_v6_init_sequence' undeclared here (not in a function); did you mean 'cookie_init_sequence'?
.cookie_init_sequence = __cookie_v6_init_sequence,
^~~~~~~~~~~~~~~~~~~~~~~~~
cookie_init_sequence
>> net/ipv6/netfilter.c:238:21: error: '__cookie_v6_check' undeclared here (not in a function); did you mean '__cookie_v4_check'?
.cookie_v6_check = __cookie_v6_check,
^~~~~~~~~~~~~~~~~
__cookie_v4_check
vim +237 net/ipv6/netfilter.c
230
231 static const struct nf_ipv6_ops ipv6ops = {
232 #if IS_MODULE(CONFIG_IPV6)
233 .chk_addr = ipv6_chk_addr,
234 .route_me_harder = ip6_route_me_harder,
235 .dev_get_saddr = ipv6_dev_get_saddr,
236 .route = __nf_ip6_route,
> 237 .cookie_init_sequence = __cookie_v6_init_sequence,
> 238 .cookie_v6_check = __cookie_v6_check,
239 #endif
240 .route_input = ip6_route_input,
241 .fragment = ip6_fragment,
242 .reroute = nf_ip6_reroute,
243 #if IS_MODULE(CONFIG_IPV6) && IS_ENABLED(CONFIG_NF_DEFRAG_IPV6)
244 .br_defrag = nf_ct_frag6_gather,
245 #endif
246 #if IS_MODULE(CONFIG_IPV6)
247 .br_fragment = br_ip6_fragment,
248 #endif
249 };
250
---
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: 44553 bytes --]
reply other threads:[~2019-06-24 19:04 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=201906250340.TX2hwmgK%lkp@intel.com \
--to=lkp@intel.com \
--cc=coreteam@netfilter.org \
--cc=ffmancera@riseup.net \
--cc=kbuild-all@01.org \
--cc=netfilter-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).