From: kbuild test robot <lkp@intel.com>
To: Florian Westphal <fw@strlen.de>
Cc: kbuild-all@01.org, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org, Pablo Neira Ayuso <pablo@netfilter.org>
Subject: [nf-next:master 20/21] include/net/netfilter/nf_queue.h:16:23: error: field 'state' has incomplete type
Date: Fri, 12 Apr 2019 10:32:56 +0800 [thread overview]
Message-ID: <201904121048.HSESQQtS%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2148 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git master
head: 223fd0adfa8af36d5d9b5d38016e579ee052f367
commit: 971502d77faa50a37c89bc6d172450294ad9a5fd [20/21] bridge: netfilter: unroll NF_HOOK helper in bridge input path
config: i386-randconfig-x014-201914 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout 971502d77faa50a37c89bc6d172450294ad9a5fd
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
In file included from net//bridge/br_input.c:19:0:
>> include/net/netfilter/nf_queue.h:16:23: error: field 'state' has incomplete type
struct nf_hook_state state;
^~~~~
vim +/state +16 include/net/netfilter/nf_queue.h
97a2d41c4 Eric Leblond 2013-12-06 8
c01cd429f Patrick McHardy 2007-12-05 9 /* Each queued (to userspace) skbuff has one of these. */
02f014d88 Patrick McHardy 2007-12-05 10 struct nf_queue_entry {
02f014d88 Patrick McHardy 2007-12-05 11 struct list_head list;
02f014d88 Patrick McHardy 2007-12-05 12 struct sk_buff *skb;
02f014d88 Patrick McHardy 2007-12-05 13 unsigned int id;
960632ece Aaron Conole 2017-08-24 14 unsigned int hook_index; /* index in hook_entries->hook[] */
02f014d88 Patrick McHardy 2007-12-05 15
1d1de89b9 David S. Miller 2015-04-03 @16 struct nf_hook_state state;
a5fedd43d Florian Westphal 2013-04-19 17 u16 size; /* sizeof(entry) + saved route keys */
a5fedd43d Florian Westphal 2013-04-19 18
a5fedd43d Florian Westphal 2013-04-19 19 /* extra space to store route keys */
c01cd429f Patrick McHardy 2007-12-05 20 };
c01cd429f Patrick McHardy 2007-12-05 21
:::::: The code at line 16 was first introduced by commit
:::::: 1d1de89b9a4746f1dd055a3b8d073dd2f962a3b6 netfilter: Use nf_hook_state in nf_queue_entry.
:::::: TO: David S. Miller <davem@davemloft.net>
:::::: CC: David S. Miller <davem@davemloft.net>
---
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: 28436 bytes --]
reply other threads:[~2019-04-12 2:33 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=201904121048.HSESQQtS%lkp@intel.com \
--to=lkp@intel.com \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--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).