From: Davide Caratti <dcaratti@redhat.com>
To: Mikko Rapeli <mikko.rapeli@iki.fi>
Cc: Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
"David S . Miller" <davem@davemloft.net>,
Florian Westphal <fw@strlen.de>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
James Morris <jmorris@namei.org>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Patrick McHardy <kaber@trash.net>,
coreteam@netfilter.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next 1/4] netfilter: nf_conntrack_tuple_common.h: fix #include
Date: Fri, 11 Nov 2016 13:02:19 +0100 [thread overview]
Message-ID: <1478865739.2571.62.camel@redhat.com> (raw)
In-Reply-To: <20161111100738.GF8342@lakka.kapsi.fi>
On Fri, 2016-11-11 at 12:07 +0200, Mikko Rapeli wrote:
> I assume also with this change it is ok to include both
> <linux/netfilter.h>
> and <linux/netfilter/nf_conntrack_tuple_common.h> userspace but what was
> the
> kernel compile error with include/net/netns/conntrack.h and
> ip_conntrack_dir?
hi Mikko, thank you for looking at this!
The problem is in patch 3/4 as I added #include
<linux/netfilter/nf_conntrack_sctp.h> in include/net/netns/conntrack.h,
but I saw similar things also with DCCP.
<...>
CC kernel/sysctl_binary.o
In file included from ./include/linux/netfilter.h:14:0,
from ./include/uapi/linux/netfilter/nf_conntrack_tuple_common.h:5,
from ./include/uapi/linux/netfilter/nf_conntrack_sctp.h:5,
from ./include/linux/netfilter/nf_conntrack_sctp.h:5,
from ./include/net/netns/conntrack.h:13,
from ./include/net/net_namespace.h:25,
from ./include/linux/init_task.h:15,
from init/init_task.c:1:
./include/linux/netdevice.h:1859:2: error: unknown type name ‘possible_net_t’
possible_net_t nd_net;
^
(possile_net_t is in net_namespace.h).
> Is there a kernel side conflict between uapi and net/netns headers?
Looks like a circular dependency is here, or nf_conntrack_tuple_common.h
is including the wrong netfilter.h. From within net/netns/conntrack.h I
can include only those UAPI files that don't include <linux/netfilter.h>
(for example, nf_conntrack_tcp.h that uses '2' instead of IP_CT_DIR_MAX).
Do you have any suggestion?
thank you in advance,
--
davide
next prev parent reply other threads:[~2016-11-11 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 14:46 [PATCH nf-next 0/4] netfilter: built-in conntrack support for DCCP, SCTP, UDPlite Davide Caratti
2016-11-10 14:46 ` [PATCH nf-next 1/4] netfilter: nf_conntrack_tuple_common.h: fix #include Davide Caratti
2016-11-11 10:07 ` Mikko Rapeli
2016-11-11 12:02 ` Davide Caratti [this message]
2016-11-14 14:01 ` Davide Caratti
2016-11-14 17:59 ` mikko.rapeli
2016-11-10 14:46 ` [PATCH nf-next 2/4] netfilter: conntrack: built-in support for DCCP Davide Caratti
2016-11-10 14:46 ` [PATCH nf-next 3/4] netfilter: conntrack: built-in support for SCTP Davide Caratti
2016-11-10 14:46 ` [PATCH nf-next 4/4] netfilter: conntrack: built-in support for UDPlite Davide Caratti
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=1478865739.2571.62.camel@redhat.com \
--to=dcaratti@redhat.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mikko.rapeli@iki.fi \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=yoshfuji@linux-ipv6.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).