* link failures with bpf_map_xxx_elem_proto calls from net/core/filiter.c
@ 2015-03-04 8:42 Or Gerlitz
2015-03-04 8:56 ` Or Gerlitz
2015-03-05 19:04 ` Daniel Borkmann
0 siblings, 2 replies; 5+ messages in thread
From: Or Gerlitz @ 2015-03-04 8:42 UTC (permalink / raw)
To: Daniel Borkmann; +Cc: Alexei Starovoitov, netdev@vger.kernel.org
Hi Daniel,
With net-next (and probably net or Linus tree too), I am getting these
link failures
net/built-in.o:(.rodata+0x2210): undefined reference to
`bpf_map_lookup_elem_proto'
net/built-in.o:(.rodata+0x2218): undefined reference to
`bpf_map_update_elem_proto'
net/built-in.o:(.rodata+0x2220): undefined reference to
`bpf_map_delete_elem_proto'
which are resolved when CONFIG_BPF_SYSCALL is added to the kernel
config, I see now t hat this 4.0-rc1 commit d4052c4aea0cf "ebpf: remove
CONFIG_BPF_SYSCALL ifdefs in socket filter code" removed the ifdefing,
not sure what does "BPF internal header can deal with it" means.
Or.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: link failures with bpf_map_xxx_elem_proto calls from net/core/filiter.c
2015-03-04 8:42 link failures with bpf_map_xxx_elem_proto calls from net/core/filiter.c Or Gerlitz
@ 2015-03-04 8:56 ` Or Gerlitz
2015-03-04 15:44 ` Alexei Starovoitov
2015-03-05 19:06 ` Daniel Borkmann
2015-03-05 19:04 ` Daniel Borkmann
1 sibling, 2 replies; 5+ messages in thread
From: Or Gerlitz @ 2015-03-04 8:56 UTC (permalink / raw)
To: Daniel Borkmann; +Cc: Alexei Starovoitov, netdev@vger.kernel.org
On 3/4/2015 10:42 AM, Or Gerlitz wrote:
> Hi Daniel,
>
> With net-next (and probably net or Linus tree too), I am getting these
> link failures
>
> net/built-in.o:(.rodata+0x2210): undefined reference to
> `bpf_map_lookup_elem_proto'
> net/built-in.o:(.rodata+0x2218): undefined reference to
> `bpf_map_update_elem_proto'
> net/built-in.o:(.rodata+0x2220): undefined reference to
> `bpf_map_delete_elem_proto'
>
suddenly solved after make clean and make, probably a leftover from the
fact that net-next was rebased tonight from 3.19 to 4.0-rc2
Or.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: link failures with bpf_map_xxx_elem_proto calls from net/core/filiter.c
2015-03-04 8:56 ` Or Gerlitz
@ 2015-03-04 15:44 ` Alexei Starovoitov
2015-03-05 19:06 ` Daniel Borkmann
1 sibling, 0 replies; 5+ messages in thread
From: Alexei Starovoitov @ 2015-03-04 15:44 UTC (permalink / raw)
To: Or Gerlitz, Daniel Borkmann; +Cc: netdev@vger.kernel.org
On 3/4/15 12:56 AM, Or Gerlitz wrote:
> On 3/4/2015 10:42 AM, Or Gerlitz wrote:
>> Hi Daniel,
>>
>> With net-next (and probably net or Linus tree too), I am getting these
>> link failures
>>
>> net/built-in.o:(.rodata+0x2210): undefined reference to
>> `bpf_map_lookup_elem_proto'
>> net/built-in.o:(.rodata+0x2218): undefined reference to
>> `bpf_map_update_elem_proto'
>> net/built-in.o:(.rodata+0x2220): undefined reference to
>> `bpf_map_delete_elem_proto'
>>
>
> suddenly solved after make clean and make, probably a leftover from the
> fact that net-next was rebased tonight from 3.19 to 4.0-rc2
that actually a real issue and Daniel has a patch that fixes it.
Will be submitted soon.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: link failures with bpf_map_xxx_elem_proto calls from net/core/filiter.c
2015-03-04 8:42 link failures with bpf_map_xxx_elem_proto calls from net/core/filiter.c Or Gerlitz
2015-03-04 8:56 ` Or Gerlitz
@ 2015-03-05 19:04 ` Daniel Borkmann
1 sibling, 0 replies; 5+ messages in thread
From: Daniel Borkmann @ 2015-03-05 19:04 UTC (permalink / raw)
To: Or Gerlitz; +Cc: Alexei Starovoitov, netdev@vger.kernel.org
On 03/04/2015 09:42 AM, Or Gerlitz wrote:
> Hi Daniel,
>
> With net-next (and probably net or Linus tree too), I am getting these link failures
>
> net/built-in.o:(.rodata+0x2210): undefined reference to `bpf_map_lookup_elem_proto'
> net/built-in.o:(.rodata+0x2218): undefined reference to `bpf_map_update_elem_proto'
> net/built-in.o:(.rodata+0x2220): undefined reference to `bpf_map_delete_elem_proto'
>
> which are resolved when CONFIG_BPF_SYSCALL is added to the kernel config, I see now t hat this 4.0-rc1 commit d4052c4aea0cf "ebpf: remove CONFIG_BPF_SYSCALL ifdefs in socket filter code" removed the ifdefing, not sure what does "BPF internal header can deal with it" means.
Sorry, I was travelling whole day yesterday.
Will send out a patch today.
Thanks,
Daniel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: link failures with bpf_map_xxx_elem_proto calls from net/core/filiter.c
2015-03-04 8:56 ` Or Gerlitz
2015-03-04 15:44 ` Alexei Starovoitov
@ 2015-03-05 19:06 ` Daniel Borkmann
1 sibling, 0 replies; 5+ messages in thread
From: Daniel Borkmann @ 2015-03-05 19:06 UTC (permalink / raw)
To: Or Gerlitz; +Cc: Alexei Starovoitov, netdev@vger.kernel.org
On 03/04/2015 09:56 AM, Or Gerlitz wrote:
> On 3/4/2015 10:42 AM, Or Gerlitz wrote:
>> Hi Daniel,
>>
>> With net-next (and probably net or Linus tree too), I am getting these link failures
>>
>> net/built-in.o:(.rodata+0x2210): undefined reference to `bpf_map_lookup_elem_proto'
>> net/built-in.o:(.rodata+0x2218): undefined reference to `bpf_map_update_elem_proto'
>> net/built-in.o:(.rodata+0x2220): undefined reference to `bpf_map_delete_elem_proto'
>
> suddenly solved after make clean and make, probably a leftover from the fact that net-next was rebased tonight from 3.19 to 4.0-rc2
Okay, I see. I got a report from Fengguang, he told me that he sees a linker issue only
on avr32 and openrisc archs.
Cooking patch to resolve it ...
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2015-03-05 19:06 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-03-04 8:42 link failures with bpf_map_xxx_elem_proto calls from net/core/filiter.c Or Gerlitz
2015-03-04 8:56 ` Or Gerlitz
2015-03-04 15:44 ` Alexei Starovoitov
2015-03-05 19:06 ` Daniel Borkmann
2015-03-05 19:04 ` Daniel Borkmann
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).