Messages in this thread | | | Date | Fri, 6 Jul 2018 17:00:37 +0200 | From | Florian Westphal <> | Subject | Re: [PATCH] netfilter: conntrack: add weak IPV6 dependency |
| |
Arnd Bergmann <arnd@arndb.de> wrote: > and that resulted in a new build failure: > > net/netfilter/nf_conntrack_proto.o:(.rodata+0x788): undefined > reference to `nf_conntrack_l4proto_icmpv6' > net/ipv6/netfilter/nf_conntrack_reasm.o: In function `nf_ct_frag6_expire': > nf_conntrack_reasm.c:(.text+0x2320): undefined reference to > `ip6_expire_frag_queue' > net/ipv6/netfilter/nf_conntrack_reasm.o: In function `nf_ct_frag6_init': > nf_conntrack_reasm.c:(.text+0x2384): undefined reference to `ip6_frag_init' > nf_conntrack_reasm.c:(.text+0x2394): undefined reference to `ip6_frag_init' > nf_conntrack_reasm.c:(.text+0x2398): undefined reference to `ip6_rhash_params' > net/ipv6/netfilter/nf_conntrack_reasm.o: In function `nf_ct_frag6_expire': > nf_conntrack_reasm.c:(.text+0x10bc): undefined reference to > `ip6_expire_frag_queue' > > I don't think we can get CONFIG_NF_DEFRAG_IPV6=y to work with IPV6=m.
Yes, not with current implementation, but I still don't think this is unavoidable.
In case this is urgent I'm fine with the patch that adds the dependency, otherwise I'd like to try and disentangle nf_conntrack_reasm and ipv6.
| |