From: Daniel Borkmann <daniel@iogearbox.net>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org
Subject: Re: [net-next:master 1077/1082] net/core/filter.c:1824:2: error: implicit declaration of function 'ip_tunnel_info_opts_get'
Date: Tue, 08 Mar 2016 21:32:27 +0100 [thread overview]
Message-ID: <56DF36DB.8060404@iogearbox.net> (raw)
In-Reply-To: <201603090421.YL50GvPu%fengguang.wu@intel.com>
On 03/08/2016 09:20 PM, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
> head: f8b33d8e870758ccff13e5f81fd5050b52a42d35
> commit: 14ca0751c96f8d3d0f52e8ed3b3236f8b34d3460 [1077/1082] bpf: support for access to tunnel options
> config: x86_64-randconfig-i0-03080544 (attached as .config)
> reproduce:
> git checkout 14ca0751c96f8d3d0f52e8ed3b3236f8b34d3460
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> All errors (new ones prefixed by >>):
>
> net/core/filter.c: In function 'bpf_skb_get_tunnel_opt':
>>> net/core/filter.c:1824:2: error: implicit declaration of function 'ip_tunnel_info_opts_get' [-Werror=implicit-function-declaration]
> ip_tunnel_info_opts_get(to, info);
> ^
> net/core/filter.c: In function 'bpf_skb_set_tunnel_opt':
>>> net/core/filter.c:1918:2: error: implicit declaration of function 'ip_tunnel_info_opts_set' [-Werror=implicit-function-declaration]
> ip_tunnel_info_opts_set(info, from, size);
> ^
> cc1: some warnings being treated as errors
Hmm, I see, it depends on CONFIG_INET, the rest of tunnel key API apparently not. :/
The attached .config here has:
# CONFIG_INET is not set
I'll send you a follow-up fix.
Thanks,
Daniel
prev parent reply other threads:[~2016-03-08 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 20:20 [net-next:master 1077/1082] net/core/filter.c:1824:2: error: implicit declaration of function 'ip_tunnel_info_opts_get' kbuild test robot
2016-03-08 20:32 ` 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=56DF36DB.8060404@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=fengguang.wu@intel.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 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.