From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net, jakub.kicinski@netronome.com
Cc: daniel@iogearbox.net, ast@kernel.org, andrii.nakryiko@gmail.com,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: pull-request: bpf 2019-08-24
Date: Sat, 24 Aug 2019 02:11:57 +0200 [thread overview]
Message-ID: <20190824001157.16043-1-daniel@iogearbox.net> (raw)
Hi David,
The following pull-request contains BPF updates for your *net* tree.
The main changes are:
1) Fix verifier precision tracking with BPF-to-BPF calls, from Alexei.
2) Fix a use-after-free in prog symbol exposure, from Daniel.
3) Several s390x JIT fixes plus BE related fixes in BPF kselftests, from Ilya.
4) Fix memory leak by unpinning XDP umem pages in error path, from Ivan.
5) Fix a potential use-after-free on flow dissector detach, from Jakub.
6) Fix bpftool to close prog fd after showing metadata, from Quentin.
7) BPF kselftest config and TEST_PROGS_EXTENDED fixes, from Anders.
Please consider pulling these changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
Thanks a lot!
----------------------------------------------------------------
The following changes since commit 125b7e0949d4e72b15c2b1a1590f8cece985a918:
net: tc35815: Explicitly check NET_IP_ALIGN is not zero in tc35815_rx (2019-08-11 21:41:48 -0700)
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 2c238177bd7f4b14bdf7447cc1cd9bb791f147e6:
bpf: allow narrow loads of some sk_reuseport_md fields with offset > 0 (2019-08-24 01:25:41 +0200)
----------------------------------------------------------------
Alexei Starovoitov (1):
bpf: fix precision tracking in presence of bpf2bpf calls
Anders Roxell (2):
selftests/bpf: add config fragment BPF_JIT
selftests/bpf: install files test_xdp_vlan.sh
Daniel Borkmann (1):
bpf: fix use after free in prog symbol exposure
Ilya Leoshkevich (6):
s390/bpf: fix lcgr instruction encoding
s390/bpf: use 32-bit index for tail calls
selftests/bpf: fix "bind{4, 6} deny specific IP & port" on s390
selftests/bpf: fix test_cgroup_storage on s390
selftests/bpf: fix test_btf_dump with O=
bpf: allow narrow loads of some sk_reuseport_md fields with offset > 0
Ivan Khoronzhuk (1):
xdp: unpin xdp umem pages in error path
Jakub Sitnicki (1):
flow_dissector: Fix potential use-after-free on BPF_PROG_DETACH
Quentin Monnet (1):
tools: bpftool: close prog FD before exit on showing a single program
arch/s390/net/bpf_jit_comp.c | 12 +++++----
kernel/bpf/syscall.c | 30 ++++++++++++++---------
kernel/bpf/verifier.c | 9 ++++---
net/core/filter.c | 8 +++---
net/core/flow_dissector.c | 2 +-
net/xdp/xdp_umem.c | 4 ++-
tools/bpf/bpftool/prog.c | 4 ++-
tools/testing/selftests/bpf/Makefile | 6 ++++-
tools/testing/selftests/bpf/config | 1 +
tools/testing/selftests/bpf/test_btf_dump.c | 7 ++++++
tools/testing/selftests/bpf/test_cgroup_storage.c | 6 ++---
tools/testing/selftests/bpf/test_sock.c | 7 ++++--
12 files changed, 62 insertions(+), 34 deletions(-)
next reply other threads:[~2019-08-24 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-24 0:11 Daniel Borkmann [this message]
2019-08-24 0:34 ` pull-request: bpf 2019-08-24 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=20190824001157.16043-1-daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.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