From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v3 bpf-next 00/10] Enhance BPF global subprogs with argument tags
Date: Wed, 20 Dec 2023 02:20:27 +0000 [thread overview]
Message-ID: <170303882712.21964.17240380114004392748.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231215011334.2307144-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 14 Dec 2023 17:13:24 -0800 you wrote:
> This patch set adds verifier support for annotating user's global BPF subprog
> arguments with few commonly requested annotations, to improve global subprog
> verification experience.
>
> These tags are:
> - ability to annotate a special PTR_TO_CTX argument;
> - ability to annotate a generic PTR_TO_MEM as non-null.
>
> [...]
Here is the summary with links:
- [v3,bpf-next,01/10] bpf: abstract away global subprog arg preparation logic from reg state setup
https://git.kernel.org/bpf/bpf-next/c/4ba1d0f23414
- [v3,bpf-next,02/10] bpf: reuse btf_prepare_func_args() check for main program BTF validation
https://git.kernel.org/bpf/bpf-next/c/5eccd2db42d7
- [v3,bpf-next,03/10] bpf: prepare btf_prepare_func_args() for handling static subprogs
https://git.kernel.org/bpf/bpf-next/c/e26080d0da87
- [v3,bpf-next,04/10] bpf: move subprog call logic back to verifier.c
https://git.kernel.org/bpf/bpf-next/c/c5a7244759b1
- [v3,bpf-next,05/10] bpf: reuse subprog argument parsing logic for subprog call checks
https://git.kernel.org/bpf/bpf-next/c/f18c3d88deed
- [v3,bpf-next,06/10] bpf: support 'arg:xxx' btf_decl_tag-based hints for global subprog args
https://git.kernel.org/bpf/bpf-next/c/94e1c70a3452
- [v3,bpf-next,07/10] bpf: add support for passing dynptr pointer to global subprog
https://git.kernel.org/bpf/bpf-next/c/a64bfe618665
- [v3,bpf-next,08/10] libbpf: add __arg_xxx macros for annotating global func args
https://git.kernel.org/bpf/bpf-next/c/aae9c25dda15
- [v3,bpf-next,09/10] selftests/bpf: add global subprog annotation tests
https://git.kernel.org/bpf/bpf-next/c/0a0ffcac92d5
- [v3,bpf-next,10/10] selftests/bpf: add freplace of BTF-unreliable main prog test
https://git.kernel.org/bpf/bpf-next/c/f0a5056222f2
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:[~2023-12-20 2:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 1:13 [PATCH v3 bpf-next 00/10] Enhance BPF global subprogs with argument tags Andrii Nakryiko
2023-12-15 1:13 ` [PATCH v3 bpf-next 01/10] bpf: abstract away global subprog arg preparation logic from reg state setup Andrii Nakryiko
2023-12-15 1:13 ` [PATCH v3 bpf-next 02/10] bpf: reuse btf_prepare_func_args() check for main program BTF validation Andrii Nakryiko
2023-12-15 1:13 ` [PATCH v3 bpf-next 03/10] bpf: prepare btf_prepare_func_args() for handling static subprogs Andrii Nakryiko
2023-12-15 1:13 ` [PATCH v3 bpf-next 04/10] bpf: move subprog call logic back to verifier.c Andrii Nakryiko
2023-12-15 1:13 ` [PATCH v3 bpf-next 05/10] bpf: reuse subprog argument parsing logic for subprog call checks Andrii Nakryiko
2023-12-15 1:13 ` [PATCH v3 bpf-next 06/10] bpf: support 'arg:xxx' btf_decl_tag-based hints for global subprog args Andrii Nakryiko
2023-12-15 1:13 ` [PATCH v3 bpf-next 07/10] bpf: add support for passing dynptr pointer to global subprog Andrii Nakryiko
2023-12-20 2:19 ` Alexei Starovoitov
2023-12-20 5:15 ` Andrii Nakryiko
2023-12-15 1:13 ` [PATCH v3 bpf-next 08/10] libbpf: add __arg_xxx macros for annotating global func args Andrii Nakryiko
2023-12-15 1:13 ` [PATCH v3 bpf-next 09/10] selftests/bpf: add global subprog annotation tests Andrii Nakryiko
2023-12-15 1:13 ` [PATCH v3 bpf-next 10/10] selftests/bpf: add freplace of BTF-unreliable main prog test Andrii Nakryiko
2023-12-20 2:20 ` 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=170303882712.21964.17240380114004392748.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=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
/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