From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Martin KaFai Lau <kafai@fb.com>, netdev@vger.kernel.org
Subject: Re: [BUG] bpf is broken in net-next
Date: Sun, 1 Oct 2017 18:34:25 -0700 [thread overview]
Message-ID: <20171002013424.tlaictbu7btc4z56@ast-mbp> (raw)
In-Reply-To: <20171001140230.6a494b48@xeon-e3>
On Sun, Oct 01, 2017 at 02:02:30PM -0700, Stephen Hemminger wrote:
> Recent regression in net-next building bpf.c in samples/bpf now broken.
>
> $ make samples/bpf/
>
>
> HOSTCC samples/bpf/../../tools/lib/bpf/bpf.o
> samples/bpf/../../tools/lib/bpf/bpf.c: In function ‘bpf_create_map_node’:
> samples/bpf/../../tools/lib/bpf/bpf.c:76:13: error: ‘union bpf_attr’ has no member named ‘map_name’; did you mean ‘map_type’?
> memcpy(attr.map_name, name, min(name_len, BPF_OBJ_NAME_LEN - 1));
> ^
> samples/bpf/../../tools/lib/bpf/bpf.c:76:44: error: ‘BPF_OBJ_NAME_LEN’ undeclared (first use in this function)
> memcpy(attr.map_name, name, min(name_len, BPF_OBJ_NAME_LEN - 1));
everything works fine for me...
did you do 'make headers_install' ?
next prev parent reply other threads:[~2017-10-02 1:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 21:02 [BUG] bpf is broken in net-next Stephen Hemminger
2017-10-02 1:34 ` Alexei Starovoitov [this message]
2017-10-02 14:52 ` Stephen Hemminger
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=20171002013424.tlaictbu7btc4z56@ast-mbp \
--to=alexei.starovoitov@gmail.com \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox