From: Hou Tao <houtao1@huawei.com>
To: Martin KaFai Lau <kafai@fb.com>, Alexei Starovoitov <ast@kernel.org>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>, <netdev@vger.kernel.org>,
<bpf@vger.kernel.org>, <houtao1@huawei.com>
Subject: [PATCH bpf-next 0/5] introduce dummy BPF STRUCT_OPS
Date: Tue, 28 Sep 2021 10:52:23 +0800 [thread overview]
Message-ID: <20210928025228.88673-1-houtao1@huawei.com> (raw)
Hi,
Currently the test of BPF STRUCT_OPS depends on the specific bpf
implementation (e.g, tcp_congestion_ops), but it can not cover all
basic functionalities (e.g, return value handling), so introduce
a dummy BPF STRUCT_OPS for test purpose.
Instead of loading a userspace-implemeted bpf_dummy_ops map into
kernel and calling the specific function by writing to sysfs provided
by bpf_testmode.ko, only loading bpf_dummy_ops related prog into
kernel and calling these prog by bpf_prog_test_run(). The latter
is more flexible and has no dependency on extra kernel module.
Now only the return value handling related test cases are supported,
if more is needed, we can add afterwards.
Comments are always welcome.
Regards,
Hou
Changelog:
* RFC: https://www.spinics.net/lists/bpf/msg46117.html
Hou Tao (5):
bpf: add dummy BPF STRUCT_OPS for test purpose
bpf: factor out a helper to prepare trampoline for struct_ops prog
bpf: do .test_run in dummy BPF STRUCT_OPS
bpf: hook .test_run for struct_ops program
selftests/bpf: test return value handling for struct_ops prog
include/linux/bpf.h | 5 +
include/linux/bpf_dummy_ops.h | 25 ++
kernel/bpf/bpf_struct_ops.c | 43 +++-
kernel/bpf/bpf_struct_ops_types.h | 2 +
net/bpf/Makefile | 3 +
net/bpf/bpf_dummy_struct_ops.c | 220 ++++++++++++++++++
.../selftests/bpf/prog_tests/dummy_st_ops.c | 81 +++++++
.../selftests/bpf/progs/dummy_st_ops.c | 33 +++
8 files changed, 403 insertions(+), 9 deletions(-)
create mode 100644 include/linux/bpf_dummy_ops.h
create mode 100644 net/bpf/bpf_dummy_struct_ops.c
create mode 100644 tools/testing/selftests/bpf/prog_tests/dummy_st_ops.c
create mode 100644 tools/testing/selftests/bpf/progs/dummy_st_ops.c
--
2.29.2
next reply other threads:[~2021-09-28 2:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 2:52 Hou Tao [this message]
2021-09-28 2:52 ` [PATCH bpf-next 1/5] bpf: add dummy BPF STRUCT_OPS for test purpose Hou Tao
2021-09-28 2:52 ` [PATCH bpf-next 2/5] bpf: factor out a helper to prepare trampoline for struct_ops prog Hou Tao
2021-09-29 17:56 ` Martin KaFai Lau
2021-09-30 10:17 ` Hou Tao
2021-10-01 17:39 ` Martin KaFai Lau
2021-09-28 2:52 ` [PATCH bpf-next 3/5] bpf: do .test_run in dummy BPF STRUCT_OPS Hou Tao
2021-09-29 18:55 ` Martin KaFai Lau
2021-09-30 11:05 ` Hou Tao
2021-10-01 19:09 ` Martin KaFai Lau
2021-09-28 2:52 ` [PATCH bpf-next 4/5] bpf: hook .test_run for struct_ops program Hou Tao
2021-09-28 2:52 ` [PATCH bpf-next 5/5] selftests/bpf: test return value handling for struct_ops prog Hou Tao
2021-09-28 23:19 ` Andrii Nakryiko
2021-09-30 11:08 ` Hou Tao
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=20210928025228.88673-1-houtao1@huawei.com \
--to=houtao1@huawei.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@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).