lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <56E05B19.5040101@iogearbox.net>
Date:	Wed, 09 Mar 2016 18:19:21 +0100
From:	Daniel Borkmann <daniel@...earbox.net>
To:	Randy Dunlap <rdunlap@...radead.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org
CC:	linux-kernel@...r.kernel.org,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: linux-next: Tree for Mar 9 (net: bpf)

On 03/09/2016 06:07 PM, Randy Dunlap wrote:
> On 03/09/16 08:48, Daniel Borkmann wrote:
>> On 03/09/2016 05:44 PM, Randy Dunlap wrote:
>>> On 03/08/16 21:38, Stephen Rothwell wrote:
>>>> Hi all,
>>>>
>>>> Changes since 20160308:
>>>
>>> on x86_64:
>>>
>>> ../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);
>>>     ^
>>> Full randconfig file is attached.
>>
>> Already fixed with net-next commit e28e87ed474c ("ip_tunnel, bpf:
>> ip_tunnel_info_opts_{get, set} depends on CONFIG_INET").
[...]
> Is that patch on the netdev mailing list or patchwork?
> I can't find it.

It is in patchwork archive or also here:

https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=e28e87ed474c5a0b378c66fb85efc8e487f4f63f

Was reported first by Fengguang's build bot i.e. his config had !CONFIG_INET
like in your case, so should resolve the issue.

Thanks,
Daniel

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ