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,
martin.lau@linux.dev, brauner@kernel.org,
torvalds@linuxfoundation.org, netdev@vger.kernel.org,
bpf@vger.kernel.org
Subject: pull-request: bpf-next 2023-12-19
Date: Tue, 19 Dec 2023 18:03:59 +0100 [thread overview]
Message-ID: <20231219170359.11035-1-daniel@iogearbox.net> (raw)
Hi David, hi Jakub, hi Paolo, hi Eric,
The following pull-request contains BPF updates for your *net-next* tree.
We've added 2 non-merge commits during the last 1 day(s) which contain
a total of 40 files changed, 642 insertions(+), 2926 deletions(-).
The main changes are:
1) Revert all of BPF token-related patches for now as per list discussion [0],
from Andrii Nakryiko.
[0] https://lore.kernel.org/bpf/CAHk-=wg7JuFYwGy=GOMbRCtOL+jwSQsdUaBsRWkDVYbxipbM5A@mail.gmail.com
2) Fix a syzbot-reported use-after-free read in nla_find() triggered from
bpf_skb_get_nlattr_nest() helper, from Jakub Kicinski.
Please consider pulling these changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git tags/for-netdev
Thanks a lot!
Also thanks to reporters, reviewers and testers of commits in this pull-request:
Simon Horman
----------------------------------------------------------------
The following changes since commit f7dd48ea76be30666f0614d6a06061185ed38c60:
Merge branch 'add-pf-vf-mailbox-support' (2023-12-19 12:00:55 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git tags/for-netdev
for you to fetch changes up to d17aff807f845cf93926c28705216639c7279110:
Revert BPF token-related functionality (2023-12-19 08:23:03 -0800)
----------------------------------------------------------------
bpf-next-for-netdev
----------------------------------------------------------------
Andrii Nakryiko (1):
Revert BPF token-related functionality
Jakub Kicinski (1):
bpf: Use nla_ok() instead of checking nla_len directly
drivers/media/rc/bpf-lirc.c | 2 +-
include/linux/bpf.h | 85 +-
include/linux/filter.h | 2 +-
include/linux/lsm_hook_defs.h | 15 +-
include/linux/security.h | 43 +-
include/uapi/linux/bpf.h | 42 -
kernel/bpf/Makefile | 2 +-
kernel/bpf/arraymap.c | 2 +-
kernel/bpf/bpf_lsm.c | 15 +-
kernel/bpf/cgroup.c | 6 +-
kernel/bpf/core.c | 3 +-
kernel/bpf/helpers.c | 6 +-
kernel/bpf/inode.c | 326 +------
kernel/bpf/syscall.c | 215 ++--
kernel/bpf/token.c | 271 -----
kernel/bpf/verifier.c | 13 +-
kernel/trace/bpf_trace.c | 2 +-
net/core/filter.c | 38 +-
net/ipv4/bpf_tcp_ca.c | 2 +-
net/netfilter/nf_bpf_link.c | 2 +-
security/security.c | 101 +-
security/selinux/hooks.c | 47 +-
tools/include/uapi/linux/bpf.h | 42 -
tools/lib/bpf/Build | 2 +-
tools/lib/bpf/bpf.c | 37 +-
tools/lib/bpf/bpf.h | 35 +-
tools/lib/bpf/btf.c | 7 +-
tools/lib/bpf/elf.c | 2 +
tools/lib/bpf/features.c | 478 ---------
tools/lib/bpf/libbpf.c | 573 ++++++++---
tools/lib/bpf/libbpf.h | 37 +-
tools/lib/bpf/libbpf.map | 1 -
tools/lib/bpf/libbpf_internal.h | 36 +-
tools/lib/bpf/libbpf_probes.c | 8 +-
tools/lib/bpf/str_error.h | 3 -
.../selftests/bpf/prog_tests/libbpf_probes.c | 4 -
.../testing/selftests/bpf/prog_tests/libbpf_str.c | 6 -
tools/testing/selftests/bpf/prog_tests/token.c | 1031 --------------------
tools/testing/selftests/bpf/progs/priv_map.c | 13 -
tools/testing/selftests/bpf/progs/priv_prog.c | 13 -
40 files changed, 642 insertions(+), 2926 deletions(-)
delete mode 100644 kernel/bpf/token.c
delete mode 100644 tools/lib/bpf/features.c
delete mode 100644 tools/testing/selftests/bpf/prog_tests/token.c
delete mode 100644 tools/testing/selftests/bpf/progs/priv_map.c
delete mode 100644 tools/testing/selftests/bpf/progs/priv_prog.c
next reply other threads:[~2023-12-19 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 17:03 Daniel Borkmann [this message]
2023-12-19 18:28 ` pull-request: bpf-next 2023-12-19 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=20231219170359.11035-1-daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=torvalds@linuxfoundation.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