Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: Leon Hwang <leon.hwang@linux.dev>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	John Fastabend <john.fastabend@gmail.com>,
	Andrii Nakryiko <andrii@kernel.org>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Kumar Kartikeya Dwivedi <memxor@gmail.com>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Song Liu <song@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	Emil Tsalapatis <emil@etsalapatis.com>,
	Shuah Khan <shuah@kernel.org>,
	Jingguo Tan <tanjingguo@huawei.com>,
	Pu Lehui <pulehui@huawei.com>, Lin Ma <malin89@huawei.com>,
	Maciej Fijalkowski <maciej.fijalkowski@intel.com>,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	kernel-patches-bot@fb.com
Subject: Re: [PATCH bpf-next 2/2] selftests/bpf: Verify no warning when close fexit link
Date: Wed, 22 Jul 2026 13:20:18 +0200	[thread overview]
Message-ID: <amCncpSCkLLJfCvR@krava> (raw)
In-Reply-To: <20260721133036.49265-3-leon.hwang@linux.dev>

On Tue, Jul 21, 2026 at 09:30:35PM +0800, Leon Hwang wrote:
> Add a test to verify that there's no WARNING when detaching fexit link by
> following the repro steps of previous commit.
> 
> Without the fix, the WARNING could be triggered by this test.
> 
> Signed-off-by: Leon Hwang <leon.hwang@linux.dev>

left 2 nits below

Acked-by: Jiri Olsa <jolsa@kernel.org>

jirka

> ---
>  .../selftests/bpf/prog_tests/tailcalls.c      | 51 +++++++++++++++++++
>  1 file changed, 51 insertions(+)
> 
> diff --git a/tools/testing/selftests/bpf/prog_tests/tailcalls.c b/tools/testing/selftests/bpf/prog_tests/tailcalls.c
> index c66037162da5..86d87d5817cf 100644
> --- a/tools/testing/selftests/bpf/prog_tests/tailcalls.c
> +++ b/tools/testing/selftests/bpf/prog_tests/tailcalls.c
> @@ -13,6 +13,8 @@
>  #include "tailcall_cgrp_storage.skel.h"
>  #include "tailcall_sleepable.skel.h"
>  #include "tailcall_callback.skel.h"
> +#include "tailcall_bpf2bpf2.skel.h"
> +#include "tailcall_bpf2bpf_fexit.skel.h"
>  
>  /* test_tailcall_1 checks basic functionality by patching multiple locations
>   * in a single program for a single tail call slot with nop->jmp, jmp->nop
> @@ -1907,6 +1909,53 @@ static void test_tailcall_callback(void)
>  	RUN_TESTS(tailcall_callback);
>  }
>  
> +static void test_tailcall_bpf2bpf_fexit_links(void)
> +{
> +	struct tailcall_bpf2bpf_fexit *skel1 = NULL, *skel2 = NULL;
> +	struct tailcall_bpf2bpf2 *skel_tc;
> +	struct bpf_link *link;
> +	int err, prog_fd;
> +
> +	skel_tc = tailcall_bpf2bpf2__open_and_load();
> +	if (!ASSERT_OK_PTR(skel_tc, "tailcall_bpf2bpf2__open_and_load"))
> +		return;
> +
> +	skel1 = tailcall_bpf2bpf_fexit__open();
> +	if (!ASSERT_OK_PTR(skel1, "tailcall_bpf2bpf_fexit__open"))
> +		goto out;
> +
> +	prog_fd = bpf_program__fd(skel_tc->progs.classifier_0);
> +	err = bpf_program__set_attach_target(skel1->progs.fexit, prog_fd, "subprog_tail");
> +	if (!ASSERT_OK(err, "bpf_program__set_attach_target"))
> +		goto out;
> +
> +	err = tailcall_bpf2bpf_fexit__load(skel1);
> +	if (!ASSERT_OK(err, "tailcall_bpf2bpf_fexit__load"))
> +		goto out;
> +
> +	link = bpf_program__attach_trace(skel1->progs.fexit);
> +	if (!ASSERT_OK_PTR(link, "bpf_program__attach_trace"))
> +		goto out;
> +	skel1->links.fexit = link;

nit, you could use skel1->links.fexit directly and remove link

> +
> +	skel2 = tailcall_bpf2bpf_fexit__open();
> +	if (!ASSERT_OK_PTR(skel2, "tailcall_bpf2bpf_fexit__open"))
> +		goto out;
> +
> +	err = bpf_program__set_attach_target(skel2->progs.fexit, prog_fd, "subprog_tail");
> +	if (!ASSERT_OK(err, "bpf_program__set_attach_target"))
> +		goto out;
> +
> +	err = tailcall_bpf2bpf_fexit__load(skel2);
> +	if (!ASSERT_OK(err, "tailcall_bpf2bpf_fexit__load"))
> +		goto out;

nit, no need to if/goto, just ASSERT_OK would be enough

> +
> +out:
> +	tailcall_bpf2bpf_fexit__destroy(skel1);
> +	tailcall_bpf2bpf_fexit__destroy(skel2);
> +	tailcall_bpf2bpf2__destroy(skel_tc);
> +}
> +
>  void test_tailcalls(void)
>  {
>  	if (test__start_subtest("tailcall_1"))
> @@ -1974,4 +2023,6 @@ void test_tailcalls(void)
>  	if (test__start_subtest("tailcall_cgrp_storage_no_storage_bridge"))
>  		test_tailcall_cgrp_storage_no_storage_bridge();
>  	test_tailcall_callback();
> +	if (test__start_subtest("tailcall_bpf2bpf_fexit_links"))
> +		test_tailcall_bpf2bpf_fexit_links();
>  }
> -- 
> 2.55.0
> 

  reply	other threads:[~2026-07-22 11:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 13:30 [PATCH bpf-next 0/2] bpf: Fix WARNING in bpf_tracing_link_release Leon Hwang
2026-07-21 13:30 ` [PATCH bpf-next 1/2] " Leon Hwang
2026-07-22 11:19   ` Jiri Olsa
2026-07-22 14:44     ` Leon Hwang
2026-07-21 13:30 ` [PATCH bpf-next 2/2] selftests/bpf: Verify no warning when close fexit link Leon Hwang
2026-07-22 11:20   ` Jiri Olsa [this message]
2026-07-22 14:45     ` Leon Hwang

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=amCncpSCkLLJfCvR@krava \
    --to=olsajiri@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=emil@etsalapatis.com \
    --cc=john.fastabend@gmail.com \
    --cc=kernel-patches-bot@fb.com \
    --cc=leon.hwang@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=maciej.fijalkowski@intel.com \
    --cc=malin89@huawei.com \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=pulehui@huawei.com \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=tanjingguo@huawei.com \
    --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