Netdev List
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Pablo Neira Ayuso" <pablo@netfilter.org>,
	"Jozsef Kadlecsik" <kadlec@blackhole.kfki.hu>,
	"Florian Westphal" <fw@strlen.de>,
	"David S. Miller" <davem@davemloft.net>,
	"Máté Eckl" <ecklm94@gmail.com>,
	"Fernando Fernandez Mancera" <ffmancera@riseup.net>,
	"Pablo M. Bermudo Garay" <pablombg@gmail.com>,
	"Felix Fietkau" <nbd@nbd.name>,
	netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netfilter: conntrack: add weak IPV6 dependency
Date: Fri, 6 Jul 2018 15:55:16 +0200	[thread overview]
Message-ID: <20180706135516.viz6pjtkdmcoqq2l@breakpoint.cc> (raw)
In-Reply-To: <20180706130005.3640993-1-arnd@arndb.de>

Arnd Bergmann <arnd@arndb.de> wrote:
> Now that the conntrack module contains code for ipv6, we can no longer
> have it built-in while IPv6 itself is a loadable module:
> 
> net/netfilter/nf_conntrack_proto.o: In function `nf_ct_netns_do_get':
> nf_conntrack_proto.c:(.text+0x88c): undefined reference to `nf_defrag_ipv6_enable'

AFAICS this is caused by

CONFIG_NF_CONNTRACK=y
CONFIG_IPV6=m
CONFIG_NF_DEFRAG_IPV6=m

This is exported via nf_defrag_ipv6.ko.

nf_defrag_ipv6 has an ipv6 dependency, but i think it might be avoidable
so this would work:

CONFIG_NF_CONNTRACK=y
CONFIG_NF_DEFRAG_IPV6=y
CONFIG_IPV6=m

  reply	other threads:[~2018-07-06 13:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 12:59 [PATCH] netfilter: conntrack: add weak IPV6 dependency Arnd Bergmann
2018-07-06 13:55 ` Florian Westphal [this message]
2018-07-06 14:50   ` Arnd Bergmann
2018-07-06 15:00     ` Florian Westphal
2018-07-06 15:14       ` Arnd Bergmann
2018-07-06 18:35       ` Florian Westphal
2018-07-09 16:50         ` Pablo Neira Ayuso
2018-07-09 20:27           ` Florian Westphal

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=20180706135516.viz6pjtkdmcoqq2l@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=arnd@arndb.de \
    --cc=coreteam@netfilter.org \
    --cc=davem@davemloft.net \
    --cc=ecklm94@gmail.com \
    --cc=ffmancera@riseup.net \
    --cc=kadlec@blackhole.kfki.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbd@nbd.name \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=pablombg@gmail.com \
    /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