From: patchwork-bot+netdevbpf@kernel.org
To: Martin KaFai Lau <martin.lau@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, yonghong.song@linux.dev,
ameryhung@gmail.com, kernel-team@meta.com
Subject: Re: [PATCH v5 bpf-next 0/9] bpf: Add gen_epilogue to bpf_verifier_ops
Date: Fri, 30 Aug 2024 01:30:31 +0000 [thread overview]
Message-ID: <172498143197.2137024.17719572149097207464.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240829210833.388152-1-martin.lau@linux.dev>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 29 Aug 2024 14:08:22 -0700 you wrote:
> From: Martin KaFai Lau <martin.lau@kernel.org>
>
> This set allows the subsystem to patch codes before BPF_EXIT.
> The verifier ops, .gen_epilogue, is added for this purpose.
> One of the use case will be in the bpf qdisc, the bpf qdisc
> subsystem can ensure the skb->dev is in the correct value.
> The bpf qdisc subsystem can either inline fixing it in the
> epilogue or call another kernel function to handle it (e.g. drop)
> in the epilogue. Another use case could be in bpf_tcp_ca.c to
> enforce snd_cwnd has valid value (e.g. positive value).
>
> [...]
Here is the summary with links:
- [v5,bpf-next,1/9] bpf: Move insn_buf[16] to bpf_verifier_env
https://git.kernel.org/bpf/bpf-next/c/6f606ffd6dd7
- [v5,bpf-next,2/9] bpf: Adjust BPF_JMP that jumps to the 1st insn of the prologue
https://git.kernel.org/bpf/bpf-next/c/d5c47719f244
- [v5,bpf-next,3/9] bpf: Add gen_epilogue to bpf_verifier_ops
https://git.kernel.org/bpf/bpf-next/c/169c31761c8d
- [v5,bpf-next,4/9] bpf: Export bpf_base_func_proto
https://git.kernel.org/bpf/bpf-next/c/866d571e6201
- [v5,bpf-next,5/9] selftests/bpf: attach struct_ops maps before test prog runs
https://git.kernel.org/bpf/bpf-next/c/a0dbf6d0b21e
- [v5,bpf-next,6/9] selftests/bpf: Test gen_prologue and gen_epilogue
https://git.kernel.org/bpf/bpf-next/c/47e69431b57a
- [v5,bpf-next,7/9] selftests/bpf: Add tailcall epilogue test
https://git.kernel.org/bpf/bpf-next/c/b191b0fd7400
- [v5,bpf-next,8/9] selftests/bpf: A pro/epilogue test when the main prog jumps back to the 1st insn
https://git.kernel.org/bpf/bpf-next/c/42fdbbde6cf4
- [v5,bpf-next,9/9] selftests/bpf: Test epilogue patching when the main prog has multiple BPF_EXIT
https://git.kernel.org/bpf/bpf-next/c/cada0bdcc471
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:[~2024-08-30 1:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 21:08 [PATCH v5 bpf-next 0/9] bpf: Add gen_epilogue to bpf_verifier_ops Martin KaFai Lau
2024-08-29 21:08 ` [PATCH v5 bpf-next 1/9] bpf: Move insn_buf[16] to bpf_verifier_env Martin KaFai Lau
2024-08-29 21:08 ` [PATCH v5 bpf-next 2/9] bpf: Adjust BPF_JMP that jumps to the 1st insn of the prologue Martin KaFai Lau
2024-08-30 0:47 ` Eduard Zingerman
2024-08-30 1:10 ` Martin KaFai Lau
2024-08-29 21:08 ` [PATCH v5 bpf-next 3/9] bpf: Add gen_epilogue to bpf_verifier_ops Martin KaFai Lau
2024-08-29 21:08 ` [PATCH v5 bpf-next 4/9] bpf: Export bpf_base_func_proto Martin KaFai Lau
2024-08-29 21:08 ` [PATCH v5 bpf-next 5/9] selftests/bpf: attach struct_ops maps before test prog runs Martin KaFai Lau
2024-08-29 21:08 ` [PATCH v5 bpf-next 6/9] selftests/bpf: Test gen_prologue and gen_epilogue Martin KaFai Lau
2024-08-29 21:08 ` [PATCH v5 bpf-next 7/9] selftests/bpf: Add tailcall epilogue test Martin KaFai Lau
2024-08-29 21:08 ` [PATCH v5 bpf-next 8/9] selftests/bpf: A pro/epilogue test when the main prog jumps back to the 1st insn Martin KaFai Lau
2024-08-29 21:08 ` [PATCH v5 bpf-next 9/9] selftests/bpf: Test epilogue patching when the main prog has multiple BPF_EXIT Martin KaFai Lau
2024-08-30 1:30 ` 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=172498143197.2137024.17719572149097207464.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@meta.com \
--cc=martin.lau@linux.dev \
--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