From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: pablo@netfilter.org, fengguang.wu@intel.com, fw@strlen.de,
netfilter-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH nf-next] netfilter: nf_conntrack: make nf_ct_zone_dflt built-in
Date: Wed, 02 Sep 2015 16:33:28 -0700 (PDT) [thread overview]
Message-ID: <20150902.163328.2105819031511147300.davem@davemloft.net> (raw)
In-Reply-To: <e3e68a263cbf95761bd3f759f458f43973741584.1441235714.git.daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Thu, 3 Sep 2015 01:26:07 +0200
> Fengguang reported, that some randconfig generated the following linker
> issue with nf_ct_zone_dflt object involved:
>
> [...]
> CC init/version.o
> LD init/built-in.o
> net/built-in.o: In function `ipv4_conntrack_defrag':
> nf_defrag_ipv4.c:(.text+0x93e95): undefined reference to `nf_ct_zone_dflt'
> net/built-in.o: In function `ipv6_defrag':
> nf_defrag_ipv6_hooks.c:(.text+0xe3ffe): undefined reference to `nf_ct_zone_dflt'
> make: *** [vmlinux] Error 1
>
> Given that configurations exist where we have a built-in part, which is
> accessing nf_ct_zone_dflt such as the two handlers nf_ct_defrag_user()
> and nf_ct6_defrag_user(), and a part that configures nf_conntrack as a
> module, we must move nf_ct_zone_dflt into a fixed, guaranteed built-in
> area when netfilter is configured in general.
>
> Therefore, split the more generic parts into a common header under
> include/linux/netfilter/ and move nf_ct_zone_dflt into the built-in
> section that already holds parts related to CONFIG_NF_CONNTRACK in the
> netfilter core. This fixes the issue on my side.
>
> Fixes: 308ac9143ee2 ("netfilter: nf_conntrack: push zone object into functions")
> Reported-by: Fengguang Wu <fengguang.wu@intel.com>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> ---
> [ Here's the 2nd one for either nf-next or net-next. I've tried various
> Kconfig combinations including the one Fengguang reported, seems to be
> okay from my side. ]
Ok I'll apply this directly too, thanks Daniel.
If Pablo and others want to fix this another way, they can send me
a relative patch.
Thanks.
prev parent reply other threads:[~2015-09-02 23:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 23:26 [PATCH nf-next] netfilter: nf_conntrack: make nf_ct_zone_dflt built-in Daniel Borkmann
2015-09-02 23:33 ` David Miller [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=20150902.163328.2105819031511147300.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=daniel@iogearbox.net \
--cc=fengguang.wu@intel.com \
--cc=fw@strlen.de \
--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).