All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Pablo Neira Ayuso <pablo@netfilter.org>,
	NetFilter <netfilter-devel@vger.kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Florian Westphal <fw@strlen.de>
Subject: linux-next: build failure after merge of the netfilter-next tree
Date: Mon, 21 Jan 2019 10:36:45 +1100	[thread overview]
Message-ID: <20190121103645.0b35e3e4@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1067 bytes --]

Hi all,

After merging the netfilter-next tree, today's linux-next build
(powerpc ppc64_defconfig) failed like this:

ERROR: ".nf_conntrack_invert_icmpv6_tuple" [net/netfilter/nf_conntrack.ko] undefined!
ERROR: ".nf_conntrack_icmpv6_packet" [net/netfilter/nf_conntrack.ko] undefined!
ERROR: ".nf_conntrack_icmpv6_init_net" [net/netfilter/nf_conntrack.ko] undefined!
ERROR: ".icmpv6_pkt_to_tuple" [net/netfilter/nf_conntrack.ko] undefined!
ERROR: ".nf_ct_gre_keymap_destroy" [net/netfilter/nf_conntrack.ko] undefined!

Caused by commit

  a47c54048162 ("netfilter: conntrack: handle builtin l4proto packet functions via direct calls")
  e2e48b471634 ("netfilter: conntrack: handle icmp pkt_to_tuple helper via direct calls")
  197c4300aec0 ("netfilter: conntrack: remove invert_tuple callback")
  2a389de86e4a ("netfilter: conntrack: remove l4proto init and get_net callbacks")
  e56894356f60 ("netfilter: conntrack: remove l4proto destroy hook")

I have used the netfilter-next tree from next-20190118 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-01-21  7:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-20 23:36 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-07-08  3:39 linux-next: build failure after merge of the netfilter-next tree Stephen Rothwell
2019-07-09  3:59 ` Stephen Rothwell
2019-06-20 13:47 Stephen Rothwell
2019-06-20 13:57 ` Pablo Neira Ayuso
2019-06-20 14:16   ` Stephen Rothwell
2019-04-12  6:37 Stephen Rothwell
2019-04-12  8:15 ` Florian Westphal
2019-04-13  4:05   ` Stephen Rothwell
2019-04-12 16:36 ` Pablo Neira Ayuso
2019-02-13  5:54 Stephen Rothwell
2018-10-15 23:41 Stephen Rothwell
2018-10-16  8:02 ` Pablo Neira Ayuso
2018-07-18  1:50 Stephen Rothwell
2016-08-18  1:56 Stephen Rothwell

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=20190121103645.0b35e3e4@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=fw@strlen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.