All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Or Gerlitz <ogerlitz@mellanox.com>
Cc: Alexei Starovoitov <ast@plumgrid.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: link failures with bpf_map_xxx_elem_proto calls from net/core/filiter.c
Date: Thu, 05 Mar 2015 20:06:34 +0100	[thread overview]
Message-ID: <54F8A93A.1040700@iogearbox.net> (raw)
In-Reply-To: <54F6C8D2.3080007@mellanox.com>

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 ...

  parent reply	other threads:[~2015-03-05 19:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2015-03-05 19:04 ` Daniel Borkmann

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=54F8A93A.1040700@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@plumgrid.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.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 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.