From: patchwork-bot+netdevbpf@kernel.org
To: KaFai Wan <kafai.wan@linux.dev>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev, kpsingh@kernel.org,
sdf@fomichev.me, haoluo@google.com, jolsa@kernel.org,
mykolal@fb.com, shuah@kernel.org, laoar.shao@gmail.com,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-kselftest@vger.kernel.org, leon.hwang@linux.dev
Subject: Re: [PATCH bpf-next v4 0/4] bpf: Show precise rejected function when attaching to __noreturn and deny list functions
Date: Tue, 29 Jul 2025 02:50:12 +0000 [thread overview]
Message-ID: <175375741226.943141.15535826817540151839.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250724151454.499040-1-kafai.wan@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 24 Jul 2025 23:14:50 +0800 you wrote:
> Show precise rejected function when attaching fexit/fmod_ret to __noreturn
> functions.
> Add log for attaching tracing programs to functions in deny list.
> Add selftest for attaching tracing programs to functions in deny list.
> Migrate fexit_noreturns case into tracing_failure test suite.
>
> changes:
> v4:
> - change tracing_deny case attaching function (Yonghong Song)
> - add Acked-by: Yafang Shao and Yonghong Song
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/4] bpf: Show precise rejected function when attaching fexit/fmod_ret to __noreturn functions
https://git.kernel.org/bpf/bpf-next/c/a5a6b29a700f
- [bpf-next,v4,2/4] bpf: Add log for attaching tracing programs to functions in deny list
https://git.kernel.org/bpf/bpf-next/c/863aab3d4dcd
- [bpf-next,v4,3/4] selftests/bpf: Add selftest for attaching tracing programs to functions in deny list
https://git.kernel.org/bpf/bpf-next/c/a32f6f17a74d
- [bpf-next,v4,4/4] selftests/bpf: Migrate fexit_noreturns case into tracing_failure test suite
https://git.kernel.org/bpf/bpf-next/c/51d3750aba79
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:[~2025-07-29 2:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 15:14 [PATCH bpf-next v4 0/4] bpf: Show precise rejected function when attaching to __noreturn and deny list functions KaFai Wan
2025-07-24 15:14 ` [PATCH bpf-next v4 1/4] bpf: Show precise rejected function when attaching fexit/fmod_ret to __noreturn functions KaFai Wan
2025-07-24 15:14 ` [PATCH bpf-next v4 2/4] bpf: Add log for attaching tracing programs to functions in deny list KaFai Wan
2025-07-24 15:14 ` [PATCH bpf-next v4 3/4] selftests/bpf: Add selftest " KaFai Wan
2025-07-24 15:14 ` [PATCH bpf-next v4 4/4] selftests/bpf: Migrate fexit_noreturns case into tracing_failure test suite KaFai Wan
2025-07-29 2:50 ` 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=175375741226.943141.15535826817540151839.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai.wan@linux.dev \
--cc=kpsingh@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=leon.hwang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).