From: Hou Tao <hotforest@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Alexei Starovoitov <ast@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Yonghong Song <yhs@fb.com>,
Andrii Nakryiko <andrii@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org, houtao1@huawei.com
Subject: [PATCH bpf-next v4 0/2] selftests: add test for kfunc call
Date: Sun, 6 Feb 2022 12:31:05 +0800 [thread overview]
Message-ID: <20220206043107.18549-1-houtao1@huawei.com> (raw)
Hi,
The patchset add a test for kfunc call to ensure s32 is sufficient for
kfunc offset. Patch #1 unexports the subtests in ksyms_module.c to fix
the confusion in test output and patch #2 adds a test in ksyms_module.c
to ensure s32 is sufficient for kfunc offset.
Change Log:
v4:
* remove merged patch "bpf, arm64: enable kfunc call"
* rebased on bpf-next
v3: https://lore.kernel.org/bpf/20220130092917.14544-1-hotforest@gmail.com
* patch #2: newly-addded to unexport unnecessary subtests
* patch #3: use kallsyms_find() instead of reimplementing it.
* patch #3: ensure kfunc call is supported before checking
whether s32 will be overflowed or not.
v2: https://lore.kernel.org/bpf/20220127071532.384888-1-houtao1@huawei.com
* add a test to check whether imm will be overflowed for kfunc call
v1: https://lore.kernel.org/bpf/20220119144942.305568-1-houtao1@huawei.com
Hou Tao (2):
selftests/bpf: do not export subtest as standalone test
selftests/bpf: check whether s32 is sufficient for kfunc offset
.../selftests/bpf/prog_tests/ksyms_module.c | 46 ++++++++++++++++++-
.../bpf/prog_tests/xdp_adjust_frags.c | 6 ---
.../bpf/prog_tests/xdp_adjust_tail.c | 4 +-
.../bpf/prog_tests/xdp_cpumap_attach.c | 4 +-
.../bpf/prog_tests/xdp_devmap_attach.c | 2 +-
5 files changed, 49 insertions(+), 13 deletions(-)
--
2.35.1
next reply other threads:[~2022-02-06 4:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 4:31 Hou Tao [this message]
2022-02-06 4:31 ` [PATCH bpf-next v4 1/2] selftests/bpf: do not export subtest as standalone test Hou Tao
2022-02-07 18:17 ` Yonghong Song
2022-02-08 1:36 ` Hou Tao
2022-02-06 4:31 ` [PATCH bpf-next v4 2/2] selftests/bpf: check whether s32 is sufficient for kfunc offset Hou Tao
2022-02-07 18:33 ` Yonghong Song
2022-02-08 2:47 ` 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=20220206043107.18549-1-houtao1@huawei.com \
--to=hotforest@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=houtao1@huawei.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yhs@fb.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).