From: Daniel Borkmann <daniel@iogearbox.net>
To: kbuild test robot <fengguang.wu@intel.com>, Jiri Benc <jbenc@redhat.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org
Subject: Re: [net-next:master 300/401] nf_defrag_ipv6_hooks.c:undefined reference to `nf_ct_zone_dflt'
Date: Wed, 02 Sep 2015 10:31:05 +0200 [thread overview]
Message-ID: <55E6B3C9.4040508@iogearbox.net> (raw)
In-Reply-To: <201509021529.WxsKStJ5%fengguang.wu@intel.com>
On 09/02/2015 09:26 AM, kbuild test robot wrote:
> Hi Jiri,
>
> It's probably a bug fix that unveils the link errors.
I'll have a look, thanks!
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
> head: 20a17bf6c04e3eca8824c930ecc55ab832558e3b
> commit: 751a587ac9f9a8bf314590fbac32d9e418060c5a [300/401] route: fix breakage after moving lwtunnel state
> config: i386-randconfig-h0-09021408 (attached as .config)
> reproduce:
> git checkout 751a587ac9f9a8bf314590fbac32d9e418060c5a
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All error/warnings (new ones prefixed by >>):
>
> net/built-in.o: In function `ipv4_conntrack_defrag':
> nf_defrag_ipv4.c:(.text+0x8e209): undefined reference to `nf_ct_zone_dflt'
> nf_defrag_ipv4.c:(.text+0x8e21c): undefined reference to `nf_ct_zone_dflt'
> nf_defrag_ipv4.c:(.text+0x8e2cb): undefined reference to `nf_ct_zone_dflt'
> net/built-in.o: In function `ipv6_defrag':
>>> nf_defrag_ipv6_hooks.c:(.text+0xdb825): undefined reference to `nf_ct_zone_dflt'
> nf_defrag_ipv6_hooks.c:(.text+0xdb846): undefined reference to `nf_ct_zone_dflt'
> net/built-in.o:nf_defrag_ipv6_hooks.c:(.text+0xdb8ff): more undefined references to `nf_ct_zone_dflt' follow
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
>
prev parent reply other threads:[~2015-09-02 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 7:26 [net-next:master 300/401] nf_defrag_ipv6_hooks.c:undefined reference to `nf_ct_zone_dflt' kbuild test robot
2015-09-02 8:31 ` Daniel Borkmann [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=55E6B3C9.4040508@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=fengguang.wu@intel.com \
--cc=jbenc@redhat.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.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).