From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: davem@davemloft.net
Cc: kuba@kernel.org, edumazet@google.com, pabeni@redhat.com,
daniel@iogearbox.net, andrii@kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, kernel-team@fb.com
Subject: pull-request: bpf 2023-11-15
Date: Wed, 15 Nov 2023 13:49:49 -0800 [thread overview]
Message-ID: <20231115214949.48854-1-alexei.starovoitov@gmail.com> (raw)
Hi David, hi Jakub, hi Paolo, hi Eric,
The following pull-request contains BPF updates for your *net* tree.
We've added 7 non-merge commits during the last 6 day(s) which contain
a total of 9 files changed, 200 insertions(+), 49 deletions(-).
The main changes are:
1) Do not allocate bpf specific percpu memory unconditionally, from Yonghong.
2) Fix precision backtracking instruction iteration, from Andrii.
3) Fix control flow graph checking, from Andrii.
4) Fix xskxceiver selftest build, from Anders.
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:
Eduard Zingerman, Hao Sun, Hou Tao
----------------------------------------------------------------
The following changes since commit 89cdf9d556016a54ff6ddd62324aa5ec790c05cc:
Merge tag 'net-6.7-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (2023-11-09 17:09:35 -0800)
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 1fda5bb66ad8fb24ecb3858e61a13a6548428898:
bpf: Do not allocate percpu memory at init stage (2023-11-15 07:51:06 -0800)
----------------------------------------------------------------
Alexei Starovoitov (1):
Merge branch 'bpf-control-flow-graph-and-precision-backtrack-fixes'
Anders Roxell (1):
selftests: bpf: xskxceiver: ksft_print_msg: fix format type error
Andrii Nakryiko (5):
bpf: handle ldimm64 properly in check_cfg()
bpf: fix precision backtracking instruction iteration
selftests/bpf: add edge case backtracking logic test
bpf: fix control-flow graph checking in privileged mode
selftests/bpf: add more test cases for check_cfg()
Yonghong Song (1):
bpf: Do not allocate percpu memory at init stage
include/linux/bpf.h | 10 ++-
kernel/bpf/core.c | 8 +-
kernel/bpf/verifier.c | 87 ++++++++++++++++------
tools/testing/selftests/bpf/progs/verifier_cfg.c | 62 +++++++++++++++
.../testing/selftests/bpf/progs/verifier_loops1.c | 9 ++-
.../selftests/bpf/progs/verifier_precision.c | 40 ++++++++++
tools/testing/selftests/bpf/verifier/calls.c | 6 +-
tools/testing/selftests/bpf/verifier/ld_imm64.c | 8 +-
tools/testing/selftests/bpf/xskxceiver.c | 19 +++--
9 files changed, 200 insertions(+), 49 deletions(-)
next reply other threads:[~2023-11-15 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 21:49 Alexei Starovoitov [this message]
2023-11-16 6:40 ` pull-request: bpf 2023-11-15 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=20231115214949.48854-1-alexei.starovoitov@gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-team@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.