From: Yonghong Song <yonghong.song@linux.dev>
To: Jiri Olsa <jolsa@kernel.org>, Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Cc: Ilya Leoshkevich <iii@linux.ibm.com>,
bpf@vger.kernel.org, Martin KaFai Lau <kafai@fb.com>,
Song Liu <songliubraving@fb.com>, Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@chromium.org>,
Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>
Subject: Re: [PATCHv3 bpf 2/2] selftests/bpf: Add test for early update in prog_array_map_poke_run
Date: Mon, 4 Dec 2023 21:16:52 -0800 [thread overview]
Message-ID: <0c2c5931-535c-49ab-86c4-275f64e5767c@linux.dev> (raw)
In-Reply-To: <20231203204851.388654-3-jolsa@kernel.org>
On 12/3/23 3:48 PM, Jiri Olsa wrote:
> Adding test that tries to trigger the BUG_ON during early map update
> in prog_array_map_poke_run function.
>
> The idea is to share prog array map between thread that constantly
> updates it and another one loading a program that uses that prog
> array.
>
> Eventually we will hit a place where the program is ok to be updated
> (poke->tailcall_target_stable check) but the address is still not
> registered in kallsyms, so the bpf_arch_text_poke returns -EINVAL
> and cause imbalance for the next tail call update check, which will
> fail with -EBUSY in bpf_arch_text_poke as described in previous fix.
>
> Acked-by: Ilya Leoshkevich <iii@linux.ibm.com>
> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> ---
> .../selftests/bpf/prog_tests/tailcall_poke.c | 74 +++++++++++++++++++
> .../selftests/bpf/progs/tailcall_poke.c | 32 ++++++++
> 2 files changed, 106 insertions(+)
> create mode 100644 tools/testing/selftests/bpf/prog_tests/tailcall_poke.c
> create mode 100644 tools/testing/selftests/bpf/progs/tailcall_poke.c
>
> diff --git a/tools/testing/selftests/bpf/prog_tests/tailcall_poke.c b/tools/testing/selftests/bpf/prog_tests/tailcall_poke.c
> new file mode 100644
> index 000000000000..f7e2c09fd772
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/prog_tests/tailcall_poke.c
> @@ -0,0 +1,74 @@
> +// SPDX-License-Identifier: GPL-2.0
> +#include <unistd.h>
> +#include <test_progs.h>
> +#include "tailcall_poke.skel.h"
> +
> +#define JMP_TABLE "/sys/fs/bpf/jmp_table"
> +
> +static int thread_exit;
> +
> +static void *update(void *arg)
> +{
> + __u32 zero = 0, prog1_fd, prog2_fd, map_fd;
> + struct tailcall_poke *call = arg;
> +
> + map_fd = bpf_map__fd(call->maps.jmp_table);
> + prog1_fd = bpf_program__fd(call->progs.call1);
> + prog2_fd = bpf_program__fd(call->progs.call2);
> +
> + while (!thread_exit) {
> + bpf_map_update_elem(map_fd, &zero, &prog1_fd, BPF_ANY);
> + bpf_map_update_elem(map_fd, &zero, &prog2_fd, BPF_ANY);
> + }
> +
> + return NULL;
> +}
> +
> +void test_tailcall_poke(void)
> +{
> + struct tailcall_poke *call, *test;
> + int err, cnt = 10;
> + pthread_t thread;
> +
> + unlink(JMP_TABLE);
> +
> + call = tailcall_poke__open_and_load();
> + if (!ASSERT_OK_PTR(call, "tailcall_poke__open"))
> + return;
> +
> + err = bpf_map__pin(call->maps.jmp_table, JMP_TABLE);
> + if (!ASSERT_OK(err, "bpf_map__pin"))
> + goto out;
Just curious. What is the reason having bpf_map__pin() here
and below? I tried and it looks like removing bpf_map__pin()
and below bpf_map__set_pin_path() will make reproducing
the failure hard/impossible.
> +
> + err = pthread_create(&thread, NULL, update, call);
> + if (!ASSERT_OK(err, "new toggler"))
> + goto out;
> +
> + while (cnt--) {
> + test = tailcall_poke__open();
> + if (!ASSERT_OK_PTR(test, "tailcall_poke__open"))
> + break;
> +
> + err = bpf_map__set_pin_path(test->maps.jmp_table, JMP_TABLE);
> + if (!ASSERT_OK(err, "bpf_map__pin")) {
> + tailcall_poke__destroy(test);
> + break;
> + }
> +
> + bpf_program__set_autoload(test->progs.test, true);
> + bpf_program__set_autoload(test->progs.call1, false);
> + bpf_program__set_autoload(test->progs.call2, false);
> +
> + err = tailcall_poke__load(test);
> + tailcall_poke__destroy(test);
> + if (!ASSERT_OK(err, "tailcall_poke__load"))
> + break;
> + }
> +
> + thread_exit = 1;
> + ASSERT_OK(pthread_join(thread, NULL), "pthread_join");
> +
> +out:
> + bpf_map__unpin(call->maps.jmp_table, JMP_TABLE);
> + tailcall_poke__destroy(call);
> +}
> diff --git a/tools/testing/selftests/bpf/progs/tailcall_poke.c b/tools/testing/selftests/bpf/progs/tailcall_poke.c
> new file mode 100644
> index 000000000000..c78b94b75e83
> --- /dev/null
> +++ b/tools/testing/selftests/bpf/progs/tailcall_poke.c
> @@ -0,0 +1,32 @@
> +// SPDX-License-Identifier: GPL-2.0
> +#include <linux/bpf.h>
> +#include <bpf/bpf_helpers.h>
> +#include <bpf/bpf_tracing.h>
> +
> +char _license[] SEC("license") = "GPL";
> +
> +struct {
> + __uint(type, BPF_MAP_TYPE_PROG_ARRAY);
> + __uint(max_entries, 1);
> + __uint(key_size, sizeof(__u32));
> + __uint(value_size, sizeof(__u32));
> +} jmp_table SEC(".maps");
> +
> +SEC("?fentry/bpf_fentry_test1")
> +int BPF_PROG(test, int a)
> +{
> + bpf_tail_call_static(ctx, &jmp_table, 0);
> + return 0;
> +}
> +
> +SEC("fentry/bpf_fentry_test1")
> +int BPF_PROG(call1, int a)
> +{
> + return 0;
> +}
> +
> +SEC("fentry/bpf_fentry_test1")
> +int BPF_PROG(call2, int a)
> +{
> + return 0;
> +}
next prev parent reply other threads:[~2023-12-05 5:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 20:48 [PATCHv3 bpf 0/2] bpf: Fix map poke update Jiri Olsa
2023-12-03 20:48 ` [PATCHv3 bpf 1/2] bpf: Fix prog_array_map_poke_run " Jiri Olsa
2023-12-05 4:52 ` Yonghong Song
2023-12-05 6:56 ` kernel test robot
2023-12-05 7:17 ` kernel test robot
2023-12-03 20:48 ` [PATCHv3 bpf 2/2] selftests/bpf: Add test for early update in prog_array_map_poke_run Jiri Olsa
2023-12-05 5:16 ` Yonghong Song [this message]
2023-12-05 8:43 ` Jiri Olsa
2023-12-05 16:00 ` Yonghong Song
2023-12-05 21:57 ` Jiri Olsa
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=0c2c5931-535c-49ab-86c4-275f64e5767c@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=iii@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@chromium.org \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--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