From: patchwork-bot+netdevbpf@kernel.org
To: sun jian <sun.jian.kdev@gmail.com>
Cc: andrii@kernel.org, shuah@kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net
Subject: Re: [PATCH v3 1/2] selftests/bpf: filter by pid to avoid cross-test interference
Date: Wed, 11 Mar 2026 16:40:09 +0000 [thread overview]
Message-ID: <177324720981.3744293.13534304462989539724.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260306083330.518627-1-sun.jian.kdev@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 6 Mar 2026 16:33:29 +0800 you wrote:
> The test installs a kprobe on __sys_connect and checks that
> bpf_probe_write_user() can modify the syscall argument. However, any
> concurrent thread in any other test that calls connect() will also
> trigger the kprobe and have its sockaddr silently overwritten, causing
> flaky failures in unrelated tests.
>
> Constrain the hook to the current test process by filtering on a PID
> stored as a global variable in .bss. Initialize the .bss value from
> user space before bpf_object__load() using bpf_map__set_initial_value(),
> and validate the bss map value size to catch layout mismatches.
>
> [...]
Here is the summary with links:
- [v3,1/2] selftests/bpf: filter by pid to avoid cross-test interference
https://git.kernel.org/bpf/bpf-next/c/70ce840d5f5b
- [v3,2/2] selftests/bpf: drop serial restriction
https://git.kernel.org/bpf/bpf-next/c/aa181c7d642c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-03-11 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 8:33 [PATCH v3 1/2] selftests/bpf: filter by pid to avoid cross-test interference Sun Jian
2026-03-06 8:33 ` [PATCH v3 2/2] selftests/bpf: drop serial restriction Sun Jian
2026-03-07 0:11 ` Kumar Kartikeya Dwivedi
2026-03-07 0:11 ` [PATCH v3 1/2] selftests/bpf: filter by pid to avoid cross-test interference Kumar Kartikeya Dwivedi
2026-03-11 16:40 ` patchwork-bot+netdevbpf [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=177324720981.3744293.13534304462989539724.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=sun.jian.kdev@gmail.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