From: patchwork-bot+netdevbpf@kernel.org
To: Sun Jian <sun.jian.kdev@gmail.com>
Cc: bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
andrii@kernel.org, shuah@kernel.org, ast@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, martin.lau@linux.dev
Subject: Re: [PATCH v2] selftests/bpf: modify_return: isolate fmod_ret hooks by pid
Date: Thu, 19 Mar 2026 00:44:01 +0000 [thread overview]
Message-ID: <177388104130.935482.1912662959372766803.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260313034540.255805-1-sun.jian.kdev@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 13 Mar 2026 11:45:40 +0800 you wrote:
> modify_return's fmod_ret programs can override bpf_modify_return_test()'s
> return value, which conflicts with get_func_ip_test when selftests run in
> parallel.
>
> Store current tgid in BSS and make modify_return hooks act only for that
> tgid. For other tasks, fentry/fexit become no-ops and fmod_ret returns the
> original ret.
>
> [...]
Here is the summary with links:
- [v2] selftests/bpf: modify_return: isolate fmod_ret hooks by pid
https://git.kernel.org/bpf/bpf-next/c/4a4fedb8a523
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-19 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 10:42 [PATCH] selftests/bpf: modify_return: isolate fmod_ret hooks by pid Sun Jian
2026-03-12 12:24 ` Jiri Olsa
2026-03-13 3:45 ` [PATCH v2] " Sun Jian
2026-03-19 0:44 ` 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=177388104130.935482.1912662959372766803.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=eddyz87@gmail.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--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