From: Andrii Nakryiko <andrii@kernel.org>
To: <davem@davemloft.net>
Cc: <kuba@kernel.org>, <pabeni@redhat.com>, <edumazet@google.com>,
<daniel@iogearbox.net>, <ast@kernel.org>,
<netdev@vger.kernel.org>, <bpf@vger.kernel.org>,
<andrii@kernel.org>, <kernel-team@fb.com>
Subject: pull-request: bpf 2022-11-11
Date: Fri, 11 Nov 2022 15:16:24 -0800 [thread overview]
Message-ID: <20221111231624.938829-1-andrii@kernel.org> (raw)
Hi David, hi Jakub, hi Paolo, hi Eric,
The following pull-request contains BPF updates for your *net* tree.
We've added 11 non-merge commits during the last 8 day(s) which contain
a total of 11 files changed, 83 insertions(+), 74 deletions(-).
The main changes are:
1) Fix strncpy_from_kernel_nofault() to prevent out-of-bounds writes,
from Alban Crequy.
2) Fix for bpf_prog_test_run_skb() to prevent wrong alignment,
from Baisong Zhong.
3) Switch BPF_DISPATCHER to static_call() instead of ftrace infra, with
a small build fix on top, from Peter Zijlstra and Nathan Chancellor.
4) Fix memory leak in BPF verifier in some error cases, from Wang Yufen.
5) 32-bit compilation error fixes for BPF selftests, from Pu Lehui and
Yang Jihong.
6) Ensure even distribution of per-CPU free list elements, from Xu Kuohai.
7) Fix copy_map_value() to track special zeroed out areas properly,
from Xu Kuohai.
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:
Andrew Morton, Björn Töpel, David Laight, Francis Laniel, Jiri Olsa,
"kernelci.org bot", kernel test robot, Kumar Kartikeya Dwivedi, Yonghong
Song
----------------------------------------------------------------
The following changes since commit 1118b2049d77ca0b505775fc1a8d1909cf19a7ec:
net: tun: Fix memory leaks of napi_get_frags (2022-11-04 10:56:22 +0000)
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 1f6e04a1c7b85da3b765ca9f46029e5d1826d839:
bpf: Fix offset calculation error in __copy_map_value and zero_map_value (2022-11-11 12:35:07 -0800)
----------------------------------------------------------------
Alban Crequy (2):
maccess: Fix writing offset in case of fault in strncpy_from_kernel_nofault()
selftests: bpf: Add a test when bpf_probe_read_kernel_str() returns EFAULT
Andrii Nakryiko (1):
Merge branch 'Fix offset when fault occurs in strncpy_from_kernel_nofault()'
Baisong Zhong (1):
bpf, test_run: Fix alignment problem in bpf_prog_test_run_skb()
Nathan Chancellor (1):
bpf: Add explicit cast to 'void *' for __BPF_DISPATCHER_UPDATE()
Peter Zijlstra (2):
bpf: Revert ("Fix dispatcher patchable function entry to 5 bytes nop")
bpf: Convert BPF_DISPATCHER to use static_call() (not ftrace)
Pu Lehui (1):
selftests/bpf: Fix casting error when cross-compiling test_verifier for 32-bit platforms
Wang Yufen (1):
bpf: Fix memory leaks in __check_func_call
Xu Kuohai (2):
bpf: Initialize same number of free nodes for each pcpu_freelist
bpf: Fix offset calculation error in __copy_map_value and zero_map_value
Yang Jihong (1):
selftests/bpf: Fix test_progs compilation failure in 32-bit arch
arch/x86/net/bpf_jit_comp.c | 13 ------
include/linux/bpf.h | 60 ++++++++++++++++---------
kernel/bpf/dispatcher.c | 28 ++++--------
kernel/bpf/percpu_freelist.c | 23 +++++-----
kernel/bpf/verifier.c | 14 +++---
mm/maccess.c | 2 +-
net/bpf/test_run.c | 1 +
tools/testing/selftests/bpf/prog_tests/varlen.c | 7 +++
tools/testing/selftests/bpf/progs/test_varlen.c | 5 +++
tools/testing/selftests/bpf/test_progs.c | 2 +-
tools/testing/selftests/bpf/test_verifier.c | 2 +-
11 files changed, 83 insertions(+), 74 deletions(-)
next reply other threads:[~2022-11-11 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 23:16 Andrii Nakryiko [this message]
2022-11-12 2:50 ` pull-request: bpf 2022-11-11 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=20221111231624.938829-1-andrii@kernel.org \
--to=andrii@kernel.org \
--cc=ast@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 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).