From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: kuba@kernel.org, daniel@iogearbox.net, andrii.nakryiko@gmail.com,
ast@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: pull-request: bpf 2021-07-29
Date: Thu, 29 Jul 2021 01:20:21 +0200 [thread overview]
Message-ID: <20210728232021.17617-1-daniel@iogearbox.net> (raw)
Hi David, hi Jakub,
The following pull-request contains BPF updates for your *net* tree.
We've added 9 non-merge commits during the last 14 day(s) which contain
a total of 20 files changed, 446 insertions(+), 138 deletions(-).
The main changes are:
1) Fix UBSAN out-of-bounds splat for showing XDP link fdinfo, from Lorenz Bauer.
2) Fix insufficient Spectre v4 mitigation in BPF runtime, from Daniel Borkmann,
Piotr Krysiuk and Benedict Schlueter.
3) Batch of fixes for BPF sockmap found under stress testing, from John Fastabend.
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 Sitnicki, Martin KaFai Lau
----------------------------------------------------------------
The following changes since commit 20192d9c9f6ae447c461285c915502ffbddf5696:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf (2021-07-15 14:39:45 -0700)
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 2039f26f3aca5b0e419b98f65dd36481337b86ee:
bpf: Fix leakage due to insufficient speculative store bypass mitigation (2021-07-29 00:27:52 +0200)
----------------------------------------------------------------
Andrii Nakryiko (1):
Merge branch 'sockmap fixes picked up by stress tests'
Daniel Borkmann (5):
bpf: Remove superfluous aux sanitation on subprog rejection
bpf: Fix pointer arithmetic mask tightening under state pruning
bpf, selftests: Add test cases for pointer alu from multiple paths
bpf: Introduce BPF nospec instruction for mitigating Spectre v4
bpf: Fix leakage due to insufficient speculative store bypass mitigation
John Fastabend (3):
bpf, sockmap: Zap ingress queues after stopping strparser
bpf, sockmap: On cleanup we additionally need to remove cached skb
bpf, sockmap: Fix memleak on ingress msg enqueue
Lorenz Bauer (1):
bpf: Fix OOB read when printing XDP link fdinfo
arch/arm/net/bpf_jit_32.c | 3 +
arch/arm64/net/bpf_jit_comp.c | 13 ++
arch/mips/net/ebpf_jit.c | 3 +
arch/powerpc/net/bpf_jit_comp32.c | 6 +
arch/powerpc/net/bpf_jit_comp64.c | 6 +
arch/riscv/net/bpf_jit_comp32.c | 4 +
arch/riscv/net/bpf_jit_comp64.c | 4 +
arch/s390/net/bpf_jit_comp.c | 5 +
arch/sparc/net/bpf_jit_comp_64.c | 3 +
arch/x86/net/bpf_jit_comp.c | 7 +
arch/x86/net/bpf_jit_comp32.c | 6 +
include/linux/bpf_types.h | 1 +
include/linux/bpf_verifier.h | 3 +-
include/linux/filter.h | 15 ++
include/linux/skmsg.h | 54 +++--
kernel/bpf/core.c | 19 +-
kernel/bpf/disasm.c | 16 +-
kernel/bpf/verifier.c | 148 +++++--------
net/core/skmsg.c | 39 +++-
.../selftests/bpf/verifier/value_ptr_arith.c | 229 +++++++++++++++++++++
20 files changed, 446 insertions(+), 138 deletions(-)
reply other threads:[~2021-07-28 23:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210728232021.17617-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=kuba@kernel.org \
--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).