From: Yonghong Song <yhs@fb.com>
To: Andrii Nakryiko <andriin@fb.com>, <bpf@vger.kernel.org>,
Martin KaFai Lau <kafai@fb.com>, <netdev@vger.kernel.org>
Cc: Alexei Starovoitov <ast@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>, <kernel-team@fb.com>
Subject: [PATCH bpf-next 0/8] misc fixes for bpf_iter
Date: Tue, 12 May 2020 08:52:32 -0700 [thread overview]
Message-ID: <20200512155232.1080167-1-yhs@fb.com> (raw)
Commit ae24345da54e ("bpf: Implement an interface to register
bpf_iter targets") and its subsequent commits in the same patch set
introduced bpf iterator, a way to run bpf program when iterating
kernel data structures.
This patch set addressed some followup issues. One big change
is to allow target to pass ctx arg register types to verifier
for verification purpose. Please see individual patch for details.
Yonghong Song (8):
tools/bpf: selftests : explain bpf_iter test failures with llvm 10.0.0
bpf: change btf_iter func proto prefix to "bpf_iter_"
bpf: add comments to interpret bpf_prog return values
bpf: add WARN_ONCE if bpf_seq_read show() return a positive number
bpf: net: refactor bpf_iter target registration
bpf: change func bpf_iter_unreg_target() signature
bpf: enable bpf_iter targets registering ctx argument types
samples/bpf: remove compiler warnings
include/linux/bpf.h | 20 +++++++++---
include/net/ip6_fib.h | 7 ++++
kernel/bpf/bpf_iter.c | 44 +++++++++++++++-----------
kernel/bpf/btf.c | 15 ++++++---
kernel/bpf/map_iter.c | 23 ++++++++------
kernel/bpf/task_iter.c | 42 ++++++++++++++++--------
kernel/bpf/verifier.c | 1 -
net/ipv6/ip6_fib.c | 5 ---
net/ipv6/route.c | 25 +++++++++------
net/netlink/af_netlink.c | 23 ++++++++------
samples/bpf/offwaketime_kern.c | 4 +--
samples/bpf/sockex2_kern.c | 4 +--
samples/bpf/sockex3_kern.c | 4 +--
tools/lib/bpf/libbpf.c | 2 +-
tools/testing/selftests/bpf/README.rst | 43 +++++++++++++++++++++++++
15 files changed, 178 insertions(+), 84 deletions(-)
create mode 100644 tools/testing/selftests/bpf/README.rst
--
2.24.1
next reply other threads:[~2020-05-12 15:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 15:52 Yonghong Song [this message]
2020-05-12 15:52 ` [PATCH bpf-next 1/8] tools/bpf: selftests : explain bpf_iter test failures with llvm 10.0.0 Yonghong Song
2020-05-12 15:52 ` [PATCH bpf-next 2/8] bpf: change btf_iter func proto prefix to "bpf_iter_" Yonghong Song
2020-05-12 22:21 ` Andrii Nakryiko
2020-05-12 15:52 ` [PATCH bpf-next 3/8] bpf: add comments to interpret bpf_prog return values Yonghong Song
2020-05-12 22:21 ` Andrii Nakryiko
2020-05-12 15:52 ` [PATCH bpf-next 4/8] bpf: add WARN_ONCE if bpf_seq_read show() return a positive number Yonghong Song
2020-05-12 22:23 ` Andrii Nakryiko
2020-05-12 15:52 ` [PATCH bpf-next 5/8] bpf: net: refactor bpf_iter target registration Yonghong Song
2020-05-12 22:19 ` Andrii Nakryiko
2020-05-12 15:52 ` [PATCH bpf-next 6/8] bpf: change func bpf_iter_unreg_target() signature Yonghong Song
2020-05-12 22:24 ` Andrii Nakryiko
2020-05-12 15:52 ` [PATCH bpf-next 7/8] bpf: enable bpf_iter targets registering ctx argument types Yonghong Song
2020-05-12 22:29 ` Andrii Nakryiko
2020-05-12 15:52 ` [PATCH bpf-next 8/8] samples/bpf: remove compiler warnings Yonghong Song
2020-05-12 22:30 ` Andrii Nakryiko
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=20200512155232.1080167-1-yhs@fb.com \
--to=yhs@fb.com \
--cc=andriin@fb.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--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).