Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: "Emil Tsalapatis" <emil@etsalapatis.com>
To: "Sun Jian" <sun.jian.kdev@gmail.com>, <bpf@vger.kernel.org>,
	<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <andrii@kernel.org>, <eddyz87@gmail.com>, <ast@kernel.org>,
	<daniel@iogearbox.net>, <martin.lau@linux.dev>, <song@kernel.org>,
	<yonghong.song@linux.dev>, <john.fastabend@gmail.com>,
	<kpsingh@kernel.org>, <sdf@fomichev.me>, <haoluo@google.com>,
	<jolsa@kernel.org>, <shuah@kernel.org>
Subject: Re: [PATCH] selftests/bpf: restrict ns_current_pid_tgid updates to target task
Date: Mon, 16 Mar 2026 10:16:03 -0400	[thread overview]
Message-ID: <DH49QO1Y58GG.2LRJUAR3P1HJT@etsalapatis.com> (raw)
In-Reply-To: <20260316073409.4040-1-sun.jian.kdev@gmail.com>

On Mon Mar 16, 2026 at 3:34 AM EDT, Sun Jian wrote:
> ns_current_pid_tgid uses a shared syscall tracepoint for
> current_pid_tgid tracepoint subtests. When selftests run in parallel,
> unrelated tasks can trigger the same hook and overwrite BSS results,
> causing false failures.
>
> Store the expected pid/tgid in BSS and update user_pid/user_tgid only
> when bpf_get_ns_current_pid_tgid() returns values matching the target
> task.
>
> This prevents unrelated tasks from interfering with the test, allows
> dropping the serial-only restriction, and removes the obsolete TODO
> comment.
>
> Tested:
>   ./test_progs -t current_pid_tgid
>   ./test_progs -j$(nproc) -t current_pid_tgid
>
> Signed-off-by: Sun Jian <sun.jian.kdev@gmail.com>

Reviewed-by: Emil Tsalapatis <emil@etsalapatis.com>

> ---
>  .../testing/selftests/bpf/prog_tests/ns_current_pid_tgid.c | 5 +++--
>  .../testing/selftests/bpf/progs/test_ns_current_pid_tgid.c | 7 +++++++
>  2 files changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/bpf/prog_tests/ns_current_pid_tgid.c b/tools/testing/selftests/bpf/prog_tests/ns_current_pid_tgid.c
> index 99c953f2be21..e3938bb48151 100644
> --- a/tools/testing/selftests/bpf/prog_tests/ns_current_pid_tgid.c
> +++ b/tools/testing/selftests/bpf/prog_tests/ns_current_pid_tgid.c
> @@ -34,6 +34,8 @@ static int get_pid_tgid(pid_t *pid, pid_t *tgid,
>  	bss->ino = st.st_ino;
>  	bss->user_pid = 0;
>  	bss->user_tgid = 0;
> +	bss->expected_pid = *pid;
> +	bss->expected_tgid = *tgid;
>  	return 0;
>  }
>  
> @@ -200,8 +202,7 @@ static void test_ns_current_pid_tgid_new_ns(int (*fn)(void *), void *arg)
>  		return;
>  }
>  
> -/* TODO: use a different tracepoint */
> -void serial_test_current_pid_tgid(void)
> +void test_current_pid_tgid(void)
>  {
>  	if (test__start_subtest("root_ns_tp"))
>  		test_current_pid_tgid_tp(NULL);
> diff --git a/tools/testing/selftests/bpf/progs/test_ns_current_pid_tgid.c b/tools/testing/selftests/bpf/progs/test_ns_current_pid_tgid.c
> index 386315afad65..d02c182a7100 100644
> --- a/tools/testing/selftests/bpf/progs/test_ns_current_pid_tgid.c
> +++ b/tools/testing/selftests/bpf/progs/test_ns_current_pid_tgid.c
> @@ -14,6 +14,8 @@ struct {
>  
>  __u64 user_pid = 0;
>  __u64 user_tgid = 0;
> +__u64 expected_pid = 0;
> +__u64 expected_tgid = 0;
>  __u64 dev = 0;
>  __u64 ino = 0;
>  
> @@ -24,6 +26,11 @@ static void get_pid_tgid(void)
>  	if (bpf_get_ns_current_pid_tgid(dev, ino, &nsdata, sizeof(struct bpf_pidns_info)))
>  		return;
>  
> +	if (expected_pid && nsdata.pid != expected_pid)
> +		return;
> +	if (expected_tgid && nsdata.tgid != expected_tgid)
> +		return;
> +
>  	user_pid = nsdata.pid;
>  	user_tgid = nsdata.tgid;
>  }
>
> base-commit: f338e77383789c0cae23ca3d48adcc5e9e137e3c


      reply	other threads:[~2026-03-16 14:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16  7:34 [PATCH] selftests/bpf: restrict ns_current_pid_tgid updates to target task Sun Jian
2026-03-16 14:16 ` Emil Tsalapatis [this message]

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=DH49QO1Y58GG.2LRJUAR3P1HJT@etsalapatis.com \
    --to=emil@etsalapatis.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --cc=sun.jian.kdev@gmail.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