netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Cong Wang <amwang@redhat.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, netdev@vger.kernel.org,
	Patrick McHardy <kaber@trash.net>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: Some netfilter compile errors when CONFIG_IPV6=m
Date: Tue, 28 May 2013 10:47:55 +0800	[thread overview]
Message-ID: <1369709275.8181.43.camel@cr0> (raw)
In-Reply-To: <20130527123339.GA16150@localhost>

On Mon, 2013-05-27 at 14:33 +0200, Pablo Neira Ayuso wrote:
> On Tue, May 14, 2013 at 10:45:52AM +0800, Cong Wang wrote:
> > Hi, all
> > 
> > I got the following compile errors when I compile IPv6 as a module and
> > most of the rest are built into core kernel. David Miller insists we
> > should fix this kind of error and not by adding Kconfig tricks.
> > 
> > net/built-in.o: In function `nf_tproxy_get_sock_v6':
> > /home/wangcong/linux/include/net/netfilter/nf_tproxy_core.h:177:
> > undefined reference to `udp6_lib_lookup'
> > /home/wangcong/linux/include/net/netfilter/nf_tproxy_core.h:177:
> > undefined reference to `udp6_lib_lookup'
> > net/built-in.o: In function `tproxy_tg_init':
> > /home/wangcong/linux/net/netfilter/xt_TPROXY.c:415: undefined reference
> > to `nf_defrag_ipv6_enable'
> > net/built-in.o: In function `socket_mt_init':
> > /home/wangcong/linux/net/netfilter/xt_socket.c:366: undefined reference
> > to `nf_defrag_ipv6_enable'
> 
> Looking at your incomplete .config, I don't see how you set xt_TPROXY
> and xt_socket but I bet they are =y.
> 
> For the udp6_lib_lookup dependency, you can use the ipv6 hooks added
> here:
> 
> commit 2a7851bffb008ff4882eee673da74718997b4265
> Author: Florian Westphal <fw@strlen.de>
> Date:   Fri May 17 03:56:10 2013 +0000
> 
>     netfilter: add nf_ipv6_ops hook to fix xt_addrtype with IPv6
> 
> Already in the nf tree, to resolve it. It would be fairly easy to make
> a patch for it.

Next time please Cc me, the reporter, when you submit a fix, otherwise I
don't know if it is fixed, since I don't subscribe nf mailing list.

> 
> For the nf_defrag_ipv6_enable, as I already mentioned, that's an
> artificial function to enforce the dependency between those two
> modules. We can add runtime checks in socket and TPROXY to skip
> further processing is nf_defrag_ipv6 is not loaded. But that's a
> problem because users will assume that their socket/TPROXY rule got
> loaded but it will not actually work since defrag is not loaded.  I
> think that really needs some Kconfig tricks for that specific case.
> 

Yeah, please send a fix? I can test it (together with my vxlan patches)
if you need. I have no cycles to work on it even if it is simple. :)

Thanks!

      reply	other threads:[~2013-05-28  2:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14  2:45 Some netfilter compile errors when CONFIG_IPV6=m Cong Wang
2013-05-14  2:48 ` Cong Wang
2013-05-14  3:10   ` Pablo Neira Ayuso
2013-05-27 10:56 ` Cong Wang
2013-05-27 12:33 ` Pablo Neira Ayuso
2013-05-28  2:47   ` Cong Wang [this message]

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=1369709275.8181.43.camel@cr0 \
    --to=amwang@redhat.com \
    --cc=davem@davemloft.net \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.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).