From: Thomas Graf <tgraf@suug.ch>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, alexei.starovoitov@gmail.com,
daniel@iogearbox.net, tom@herbertland.com,
roopa@cumulusnetworks.com
Subject: Re: [PATCH net-next v2 5/5] lwtunnel: Limit number of recursions on output to 5
Date: Tue, 1 Nov 2016 09:09:00 +0100 [thread overview]
Message-ID: <20161101080900.GA13415@pox.localdomain> (raw)
In-Reply-To: <201611011209.dx1fkD00%fengguang.wu@intel.com>
On 11/01/16 at 12:52pm, kbuild test robot wrote:
> Hi Thomas,
>
> [auto build test ERROR on net-next/master]
>
> url: https://github.com/0day-ci/linux/commits/Thomas-Graf/bpf-BPF-for-lightweight-tunnel-encapsulation/20161101-084038
> config: arm64-allmodconfig (attached as .config)
> compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # save the attached .config to linux build tree
> make.cross ARCH=arm64
>
> All errors (new ones prefixed by >>):
>
> net/built-in.o: In function `bpf_output':
> >> ncsi-manage.c:(.text+0x8e9f4): undefined reference to `ip6_route_output_flags'
Needs
depends on IPV6_MULTIPLE_TABLES || IPV6=n
Compile testing with IPV6=y and IPV6_MULTIPLE_TABLES=n would have been
great. I'll submit a v3 after some time has passed to review the new
rerouting bits.
next prev parent reply other threads:[~2016-11-01 8:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 0:37 [PATCH net-next v2 0/5] bpf: BPF for lightweight tunnel encapsulation Thomas Graf
2016-11-01 0:37 ` [PATCH net-next v2 1/5] route: Set orig_output when redirecting to lwt on locally generated traffic Thomas Graf
2016-11-01 0:37 ` [PATCH net-next v2 2/5] route: Set lwtstate for local traffic and cached input dsts Thomas Graf
2016-11-01 0:37 ` [PATCH net-next v2 3/5] bpf: BPF for lightweight tunnel encapsulation Thomas Graf
2016-11-01 1:10 ` kbuild test robot
2016-11-01 2:39 ` kbuild test robot
2016-11-01 20:11 ` David Ahern
2016-11-01 21:03 ` Thomas Graf
2016-11-02 13:39 ` Roopa Prabhu
2016-11-02 22:58 ` Thomas Graf
2016-11-01 0:37 ` [PATCH net-next v2 4/5] bpf: Add samples for LWT-BPF Thomas Graf
2016-11-01 0:37 ` [PATCH net-next v2 5/5] lwtunnel: Limit number of recursions on output to 5 Thomas Graf
2016-11-01 4:52 ` kbuild test robot
2016-11-01 8:09 ` Thomas Graf [this message]
2016-11-01 10:54 ` [PATCH net-next v2 0/5] bpf: BPF for lightweight tunnel encapsulation Hannes Frederic Sowa
2016-11-01 18:51 ` Thomas Graf
2016-11-01 20:08 ` Hannes Frederic Sowa
2016-11-01 20:59 ` Thomas Graf
2016-11-01 22:12 ` Hannes Frederic Sowa
2016-11-01 23:07 ` Tom Herbert
2016-11-02 10:48 ` Hannes Frederic Sowa
2016-11-02 16:59 ` Tom Herbert
2016-11-03 14:16 ` Thomas Graf
2016-11-02 22:57 ` Thomas Graf
2016-11-02 23:27 ` Tom Herbert
2016-11-02 22:54 ` Thomas Graf
2016-11-03 14:52 ` Hannes Frederic Sowa
2016-11-03 15:20 ` Thomas Graf
2016-11-01 16:17 ` Tom Herbert
2016-11-01 18:20 ` Thomas Graf
2016-11-01 18:51 ` Tom Herbert
2016-11-01 19:11 ` Thomas Graf
2016-11-01 19:27 ` Tom Herbert
2016-11-01 19:59 ` Thomas Graf
2016-11-01 20:33 ` Tom Herbert
2016-11-01 21:05 ` Thomas Graf
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=20161101080900.GA13415@pox.localdomain \
--to=tgraf@suug.ch \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=tom@herbertland.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;
as well as URLs for NNTP newsgroup(s).