From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: kuba@kernel.org, pabeni@redhat.com, edumazet@google.com,
daniel@iogearbox.net, ast@kernel.org, andrii@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: pull-request: bpf 2022-06-09
Date: Thu, 9 Jun 2022 01:41:33 +0200 [thread overview]
Message-ID: <20220608234133.32265-1-daniel@iogearbox.net> (raw)
Hi David, hi Jakub, hi Paolo, hi Eric,
The following pull-request contains BPF updates for your *net* tree.
We've added 6 non-merge commits during the last 2 day(s) which contain
a total of 8 files changed, 49 insertions(+), 15 deletions(-).
The main changes are:
1) Fix an illegal copy_to_user() attempt seen by syzkaller through arm64
BPF JIT compiler, from Eric Dumazet.
2) Fix calling global functions from BPF_PROG_TYPE_EXT programs by using
the correct program context type, from Toke Høiland-Jørgensen.
3) Fix XSK TX batching invalid descriptor handling, from Maciej Fijalkowski.
4) Fix potential integer overflows in multi-kprobe link code by using safer
kvmalloc_array() allocation helpers, from Dan Carpenter.
5) Add Quentin as bpftool maintainer, from Quentin Monnet.
Please consider pulling these changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
Thanks a lot!
Also thanks to reporters, reviewers and testers of commits in this pull-request:
Alexei Starovoitov, Jakub Kicinski, KP Singh, Magnus Karlsson, Simon
Sundberg, Song Liu, syzbot
----------------------------------------------------------------
The following changes since commit cf67838c4422eab826679b076dad99f96152b4de:
selftests net: fix bpf build error (2022-06-07 13:19:51 +0200)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
for you to fetch changes up to 7c217aca85dd31dd2c8f45f6a7520767c9fae766:
MAINTAINERS: Add a maintainer for bpftool (2022-06-08 17:16:34 +0200)
----------------------------------------------------------------
Dan Carpenter (1):
bpf: Use safer kvmalloc_array() where possible
Eric Dumazet (1):
bpf, arm64: Clear prog->jited_len along prog->jited
Maciej Fijalkowski (1):
xsk: Fix handling of invalid descriptors in XSK TX batching API
Quentin Monnet (1):
MAINTAINERS: Add a maintainer for bpftool
Toke Høiland-Jørgensen (2):
bpf: Fix calling global functions from BPF_PROG_TYPE_EXT programs
selftests/bpf: Add selftest for calling global functions from freplace
MAINTAINERS | 7 +++++++
arch/arm64/net/bpf_jit_comp.c | 1 +
kernel/bpf/btf.c | 3 ++-
kernel/trace/bpf_trace.c | 8 ++++----
net/xdp/xsk.c | 5 +++--
net/xdp/xsk_queue.h | 8 --------
tools/testing/selftests/bpf/prog_tests/fexit_bpf2bpf.c | 14 ++++++++++++++
.../testing/selftests/bpf/progs/freplace_global_func.c | 18 ++++++++++++++++++
8 files changed, 49 insertions(+), 15 deletions(-)
create mode 100644 tools/testing/selftests/bpf/progs/freplace_global_func.c
next reply other threads:[~2022-06-08 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 23:41 Daniel Borkmann [this message]
2022-06-09 3:40 ` pull-request: bpf 2022-06-09 patchwork-bot+netdevbpf
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=20220608234133.32265-1-daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox