From: Alexei Starovoitov <ast@kernel.org>
To: <davem@davemloft.net>
Cc: <daniel@iogearbox.net>, <netdev@vger.kernel.org>, <kernel-team@fb.com>
Subject: pull-request: bpf 2018-02-02
Date: Fri, 2 Feb 2018 18:09:13 -0800 [thread overview]
Message-ID: <20180203020913.2805851-1-ast@kernel.org> (raw)
Hi David,
The following pull-request contains BPF updates for your *net* tree.
The main changes are:
1) support XDP attach in libbpf, from Eric.
2) minor fixes, from Daniel, Jakub, Yonghong, Alexei.
Please consider pulling these changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
Should be no merge conflicts.
Thanks a lot!
----------------------------------------------------------------
The following changes since commit b2fe5fa68642860e7de76167c3111623aa0d5de1:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next (2018-01-31 14:31:10 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
for you to fetch changes up to 09c0656dfabd0b15e410eca67dc45cb14ec9c13a:
Merge branch 'libbpf-xdp-support' (2018-02-02 17:53:49 -0800)
----------------------------------------------------------------
Alexei Starovoitov (2):
bpf: fix bpf_prog_array_copy_to_user() issues
Merge branch 'libbpf-xdp-support'
Daniel Borkmann (1):
bpf: fix null pointer deref in bpf_prog_test_run_xdp
Eric Leblond (5):
tools: add netlink.h and if_link.h in tools uapi
libbpf: add function to setup XDP
libbpf: add error reporting in XDP
libbpf: add missing SPDX-License-Identifier
samples/bpf: use bpf_set_link_xdp_fd
Jakub Kicinski (1):
netdevsim: fix overflow on the error path
Yonghong Song (2):
tools/bpf: permit selftests/bpf to be built in a different directory
bpf: add documentation to compare clang "-target bpf" and default target
Documentation/bpf/bpf_devel_QA.txt | 31 +
drivers/net/netdevsim/bpf.c | 5 +-
include/linux/netdevice.h | 6 +
kernel/bpf/core.c | 32 +-
net/bpf/test_run.c | 4 +
samples/bpf/Makefile | 2 +-
samples/bpf/bpf_load.c | 102 ---
samples/bpf/bpf_load.h | 2 +-
samples/bpf/xdp1_user.c | 4 +-
samples/bpf/xdp_redirect_cpu_user.c | 6 +-
samples/bpf/xdp_redirect_map_user.c | 8 +-
samples/bpf/xdp_redirect_user.c | 8 +-
samples/bpf/xdp_router_ipv4_user.c | 10 +-
samples/bpf/xdp_rxq_info_user.c | 4 +-
samples/bpf/xdp_tx_iptunnel_user.c | 6 +-
tools/include/uapi/linux/if_link.h | 943 ++++++++++++++++++++++++++++
tools/include/uapi/linux/netlink.h | 251 ++++++++
tools/lib/bpf/Build | 2 +-
tools/lib/bpf/Makefile | 6 +
tools/lib/bpf/bpf.c | 135 ++++
tools/lib/bpf/bpf.h | 2 +
tools/lib/bpf/libbpf.c | 4 +
tools/lib/bpf/libbpf.h | 6 +
tools/lib/bpf/nlattr.c | 187 ++++++
tools/lib/bpf/nlattr.h | 72 +++
tools/testing/selftests/bpf/.gitignore | 1 +
tools/testing/selftests/bpf/Makefile | 4 +-
tools/testing/selftests/bpf/test_verifier.c | 14 +
28 files changed, 1716 insertions(+), 141 deletions(-)
create mode 100644 tools/include/uapi/linux/if_link.h
create mode 100644 tools/include/uapi/linux/netlink.h
create mode 100644 tools/lib/bpf/nlattr.c
create mode 100644 tools/lib/bpf/nlattr.h
next reply other threads:[~2018-02-03 2:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 2:09 Alexei Starovoitov [this message]
2018-02-04 21:50 ` pull-request: bpf 2018-02-02 David Miller
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=20180203020913.2805851-1-ast@kernel.org \
--to=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@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 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).