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, netdev@vger.kernel.org,
bpf@vger.kernel.org
Subject: pull-request: bpf 2024-03-06
Date: Wed, 6 Mar 2024 23:03:09 +0100 [thread overview]
Message-ID: <20240306220309.13534-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 5 non-merge commits during the last 1 day(s) which contain
a total of 5 files changed, 77 insertions(+), 4 deletions(-).
The main changes are:
1) Fix BPF verifier to check bpf_func_state->callback_depth when pruning
states as otherwise unsafe programs could get accepted, from Eduard Zingerman.
2) Fix to zero-initialise xdp_rxq_info struct before running XDP program in
CPU map which led to random xdp_md fields, from Toke Høiland-Jørgensen.
3) Fix bonding XDP feature flags calculation when bonding device has no
slave devices anymore, from Daniel Borkmann.
Please consider pulling these changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git tags/for-netdev
Thanks a lot!
Also thanks to reporters, reviewers and testers of commits in this pull-request:
Tobias Böhm, Toke Høiland-Jørgensen, Yonghong Song
----------------------------------------------------------------
The following changes since commit 685f7d531264599b3f167f1e94bbd22f120e5fab:
net/ipv6: avoid possible UAF in ip6_route_mpath_notify() (2024-03-05 11:16:11 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git tags/for-netdev
for you to fetch changes up to 2487007aa3b9fafbd2cb14068f49791ce1d7ede5:
cpumap: Zero-initialise xdp_rxq_info struct before running XDP program (2024-03-05 16:48:53 -0800)
----------------------------------------------------------------
bpf-for-netdev
----------------------------------------------------------------
Alexei Starovoitov (1):
Merge branch 'check-bpf_func_state-callback_depth-when-pruning-states'
Daniel Borkmann (2):
xdp, bonding: Fix feature flags when there are no slave devs anymore
selftests/bpf: Fix up xdp bonding test wrt feature flags
Eduard Zingerman (2):
bpf: check bpf_func_state->callback_depth when pruning states
selftests/bpf: test case for callback_depth states pruning logic
Toke Høiland-Jørgensen (1):
cpumap: Zero-initialise xdp_rxq_info struct before running XDP program
drivers/net/bonding/bond_main.c | 2 +-
kernel/bpf/cpumap.c | 2 +-
kernel/bpf/verifier.c | 3 +
.../testing/selftests/bpf/prog_tests/xdp_bonding.c | 4 +-
.../bpf/progs/verifier_iterating_callbacks.c | 70 ++++++++++++++++++++++
5 files changed, 77 insertions(+), 4 deletions(-)
next reply other threads:[~2024-03-06 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 22:03 Daniel Borkmann [this message]
2024-03-07 4:30 ` pull-request: bpf 2024-03-06 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=20240306220309.13534-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=martin.lau@linux.dev \
--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