From: Tejun Heo <tj@kernel.org>
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@fb.com, Martin KaFai Lau <martin.lau@kernel.org>
Subject: Re: [PATCH bpf-next v7 9/9] selftests/bpf: Add struct_ops prog private stack tests
Date: Wed, 30 Oct 2024 13:29:11 -1000 [thread overview]
Message-ID: <ZyLBR8cM_UhrFOBO@slm.duckdns.org> (raw)
In-Reply-To: <20241029221723.268595-1-yonghong.song@linux.dev>
Hello,
On Tue, Oct 29, 2024 at 03:17:23PM -0700, Yonghong Song wrote:
> The third test is the same callback function recursing itself. At run time,
> the jit trampoline recursion check kicks in to prevent the recursion.
>
> Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
> ---
> .../selftests/bpf/bpf_testmod/bpf_testmod.c | 94 ++++++++++++++++
> .../selftests/bpf/bpf_testmod/bpf_testmod.h | 5 +
> .../bpf/prog_tests/struct_ops_private_stack.c | 106 ++++++++++++++++++
> .../bpf/progs/struct_ops_private_stack.c | 62 ++++++++++
> .../bpf/progs/struct_ops_private_stack_fail.c | 62 ++++++++++
> .../progs/struct_ops_private_stack_recur.c | 50 +++++++++
> 6 files changed, 379 insertions(+)
> create mode 100644 tools/testing/selftests/bpf/prog_tests/struct_ops_private_stack.c
> create mode 100644 tools/testing/selftests/bpf/progs/struct_ops_private_stack.c
> create mode 100644 tools/testing/selftests/bpf/progs/struct_ops_private_stack_fail.c
> create mode 100644 tools/testing/selftests/bpf/progs/struct_ops_private_stack_recur.c
>
> diff --git a/tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c b/tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c
> index 8835761d9a12..eb761645551a 100644
> --- a/tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c
> +++ b/tools/testing/selftests/bpf/bpf_testmod/bpf_testmod.c
...
> +__bpf_kfunc void bpf_testmod_ops3_call_test_1(void)
> +{
> + st_ops3->test_1();
> +}
...
> diff --git a/tools/testing/selftests/bpf/prog_tests/struct_ops_private_stack.c b/tools/testing/selftests/bpf/prog_tests/struct_ops_private_stack.c
> new file mode 100644
> index 000000000000..4006879ca3fe
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/prog_tests/struct_ops_private_stack.c
...
> +static void test_private_stack_recur(void)
> +{
> + struct struct_ops_private_stack_recur *skel;
> + struct bpf_link *link;
> + int err;
> +
> + skel = struct_ops_private_stack_recur__open();
> + if (!ASSERT_OK_PTR(skel, "struct_ops_private_stack_recur__open"))
> + return;
> +
> + if (skel->data->skip) {
> + test__skip();
> + goto cleanup;
> + }
> +
> + err = struct_ops_private_stack_recur__load(skel);
> + if (!ASSERT_OK(err, "struct_ops_private_stack_recur__load"))
> + goto cleanup;
> +
> + link = bpf_map__attach_struct_ops(skel->maps.testmod_1);
> + if (!ASSERT_OK_PTR(link, "attach_struct_ops"))
> + goto cleanup;
> +
> + ASSERT_OK(trigger_module_test_read(256), "trigger_read");
> +
> + ASSERT_EQ(skel->bss->val_j, 3, "val_j");
> +
> + bpf_link__destroy(link);
> +
> +cleanup:
> + struct_ops_private_stack_recur__destroy(skel);
> +}
...
> diff --git a/tools/testing/selftests/bpf/progs/struct_ops_private_stack_recur.c b/tools/testing/selftests/bpf/progs/struct_ops_private_stack_recur.c
> new file mode 100644
> index 000000000000..15d4e914dc92
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/progs/struct_ops_private_stack_recur.c
> @@ -0,0 +1,50 @@
> +// SPDX-License-Identifier: GPL-2.0
> +
> +#include <vmlinux.h>
> +#include <bpf/bpf_helpers.h>
> +#include <bpf/bpf_tracing.h>
> +#include "../bpf_testmod/bpf_testmod.h"
> +
> +char _license[] SEC("license") = "GPL";
> +
> +#if defined(__TARGET_ARCH_x86)
> +bool skip __attribute((__section__(".data"))) = false;
> +#else
> +bool skip = true;
> +#endif
> +
> +void bpf_testmod_ops3_call_test_1(void) __ksym;
> +
> +int val_i, val_j;
> +
> +__noinline static int subprog2(int *a, int *b)
> +{
> + return val_i + a[10] + b[20];
> +}
> +
> +__noinline static int subprog1(int *a)
> +{
> + /* stack size 400 bytes */
> + int b[100] = {};
> +
> + b[20] = 2;
> + return subprog2(a, b);
> +}
> +
> +
> +SEC("struct_ops")
> +int BPF_PROG(test_1)
> +{
> + /* stack size 400 bytes */
> + int a[100] = {};
> +
> + a[10] = 1;
> + val_j += subprog1(a);
> + bpf_testmod_ops3_call_test_1();
> + return 0;
> +}
> +
> +SEC(".struct_ops")
> +struct bpf_testmod_ops3 testmod_1 = {
> + .test_1 = (void *)test_1,
> +};
This is delta, and, while this shouldn't happen for SCX, it'd be great if
SCX can tell BPF to call a function when recursion check triggers and
ignores a call, so that SCX can trigger error, report it and eject the
scheduler.
Thanks.
--
tejun
next prev parent reply other threads:[~2024-10-30 23:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 22:16 [PATCH bpf-next v7 0/9] bpf: Support private stack for bpf progs Yonghong Song
2024-10-29 22:16 ` [PATCH bpf-next v7 1/9] bpf: Check stack depth limit after visiting all subprogs Yonghong Song
2024-10-29 22:16 ` [PATCH bpf-next v7 2/9] bpf: Allow private stack to have each subprog having stack size of 512 bytes Yonghong Song
2024-10-29 22:16 ` [PATCH bpf-next v7 3/9] bpf: Check potential private stack recursion for progs with async callback Yonghong Song
2024-10-29 22:16 ` [PATCH bpf-next v7 4/9] bpf: Allocate private stack for eligible main prog or subprogs Yonghong Song
2024-10-29 22:17 ` [PATCH bpf-next v7 5/9] bpf, x86: Avoid repeated usage of bpf_prog->aux->stack_depth Yonghong Song
2024-10-29 22:17 ` [PATCH bpf-next v7 6/9] bpf, x86: Support private stack in jit Yonghong Song
2024-10-29 22:17 ` [PATCH bpf-next v7 7/9] selftests/bpf: Add tracing prog private stack tests Yonghong Song
2024-10-29 22:17 ` [PATCH bpf-next v7 8/9] bpf: Support private stack for struct_ops progs Yonghong Song
2024-10-30 23:14 ` Tejun Heo
2024-10-29 22:17 ` [PATCH bpf-next v7 9/9] selftests/bpf: Add struct_ops prog private stack tests Yonghong Song
2024-10-30 23:29 ` Tejun Heo [this message]
2024-10-31 19:37 ` Yonghong Song
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=ZyLBR8cM_UhrFOBO@slm.duckdns.org \
--to=tj@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=yonghong.song@linux.dev \
/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