linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	netfilter-devel@vger.kernel.org,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: linux-next: Tree for Sep 4 (netfilter: xt_TPROXY)
Date: Wed, 4 Sep 2013 23:09:40 +0200	[thread overview]
Message-ID: <20130904210940.GP32493@breakpoint.cc> (raw)
In-Reply-To: <52277212.5020006@infradead.org>

Randy Dunlap <rdunlap@infradead.org> wrote:
> On 09/04/13 01:13, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Please do not add any code for v3.13 to your linux-next included branches
> > until after v3.12-rc1 is released.
> > 
> > Changes since 20130902:
> > 
> 
> on x86_64:
> 
> when CONFIG_IPV6=m
> and CONFIG_NETFILTER_XT_TARGET_TPROXY=y:
> 
> net/built-in.o: In function `tproxy_tg6_v1':
> xt_TPROXY.c:(.text+0x5dc05): undefined reference to `udp6_lib_lookup'
> xt_TPROXY.c:(.text+0x5e32f): undefined reference to `udp6_lib_lookup'
> xt_TPROXY.c:(.text+0x5e432): undefined reference to `udp6_lib_lookup'
> net/built-in.o: In function `tproxy_tg_init':
> xt_TPROXY.c:(.init.text+0x1540): undefined reference to `nf_defrag_ipv6_enable'

Thanks for reporting.

I can reproduce same error with 3.10.6 stable tree, so its not
a recent problem.

As always, the tempting solution is to just forbid TPROXY=y with IPV6=m but
it would be better to get rid of the ipv6 link time deps..

  reply	other threads:[~2013-09-04 21:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04  8:13 linux-next: Tree for Sep 4 Stephen Rothwell
2013-09-04 17:46 ` linux-next: Tree for Sep 4 (netfilter: xt_TPROXY) Randy Dunlap
2013-09-04 21:09   ` Florian Westphal [this message]
     [not found] ` <20130904181300.06fbf0698863cfaacf9fad9a-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2013-09-04 18:01   ` [PATCH -next] bcache: fix btree printk format warning Randy Dunlap
     [not found]     ` <52277576.5020805-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2013-09-04 18:59       ` Kent Overstreet

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=20130904210940.GP32493@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    /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).