From: Stephen Hemminger <stephen@networkplumber.org>
To: Martin KaFai Lau <kafai@fb.com>
Cc: netdev@vger.kernel.org
Subject: [BUG] bpf is broken in net-next
Date: Sun, 1 Oct 2017 14:02:30 -0700 [thread overview]
Message-ID: <20171001140230.6a494b48@xeon-e3> (raw)
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));
^
samples/bpf/../../tools/lib/bpf/bpf.c:49:27: note: in definition of macro ‘min’
#define min(x, y) ((x) < (y) ? (x) : (y))
^
samples/bpf/../../tools/lib/bpf/bpf.c:76:44: note: each undeclared identifier is reported only once for each function it appears in
memcpy(attr.map_name, name, min(name_len, BPF_OBJ_NAME_LEN - 1));
^
samples/bpf/../../tools/lib/bpf/bpf.c:49:27: note: in definition of macro ‘min’
#define min(x, y) ((x) < (y) ? (x) : (y))
^
samples/bpf/../../tools/lib/bpf/bpf.c: In function ‘bpf_create_map_in_map_node’:
samples/bpf/../../tools/lib/bpf/bpf.c:116: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:116: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));
^
samples/bpf/../../tools/lib/bpf/bpf.c:49:27: note: in definition of macro ‘min’
#define min(x, y) ((x) < (y) ? (x) : (y))
^
samples/bpf/../../tools/lib/bpf/bpf.c: In function ‘bpf_load_program_name’:
samples/bpf/../../tools/lib/bpf/bpf.c:154:13: error: ‘union bpf_attr’ has no member named ‘prog_name’; did you mean ‘prog_type’?
memcpy(attr.prog_name, name, min(name_len, BPF_OBJ_NAME_LEN - 1));
^
samples/bpf/../../tools/lib/bpf/bpf.c:154:45: error: ‘BPF_OBJ_NAME_LEN’ undeclared (first use in this function)
memcpy(attr.prog_name, name, min(name_len, BPF_OBJ_NAME_LEN - 1));
^
samples/bpf/../../tools/lib/bpf/bpf.c:49:27: note: in definition of macro ‘min’
#define min(x, y) ((x) < (y) ? (x) : (y))
^
scripts/Makefile.host:118: recipe for target 'samples/bpf/../../tools/lib/bpf/bpf.o' failed
next reply other threads:[~2017-10-01 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 21:02 Stephen Hemminger [this message]
2017-10-02 1:34 ` [BUG] bpf is broken in net-next Alexei Starovoitov
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=20171001140230.6a494b48@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=kafai@fb.com \
--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.