From: patchwork-bot+netdevbpf@kernel.org
To: KP Singh <kpsingh@kernel.org>
Cc: bpf@vger.kernel.org, linux-security-module@vger.kernel.org,
bboscaccy@linux.microsoft.com, paul@paul-moore.com,
kys@microsoft.com, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org
Subject: Re: [PATCH v4 00/12] Signed BPF programs
Date: Fri, 19 Sep 2025 02:20:13 +0000 [thread overview]
Message-ID: <175824841300.3021819.875187543538843071.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250914215141.15144-1-kpsingh@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 14 Sep 2025 23:51:29 +0200 you wrote:
> # v3 -> v4
>
> * Dropped the use of session keyring by default from skeletons.
> * Andrii's feedback on exclusive map creation libbpf changes.
> * Cleaned up some more typos I found.
>
> # v2 -> v3
>
> [...]
Here is the summary with links:
- [v4,01/12] bpf: Update the bpf_prog_calc_tag to use SHA256
(no matching commit)
- [v4,02/12] bpf: Implement exclusive map creation
https://git.kernel.org/bpf/bpf-next/c/baefdbdf6812
- [v4,03/12] libbpf: Implement SHA256 internal helper
https://git.kernel.org/bpf/bpf-next/c/c297fe3e9f99
- [v4,04/12] libbpf: Support exclusive map creation
https://git.kernel.org/bpf/bpf-next/c/567010a5478f
- [v4,05/12] selftests/bpf: Add tests for exclusive maps
https://git.kernel.org/bpf/bpf-next/c/6c850cbca82c
- [v4,06/12] bpf: Return hashes of maps in BPF_OBJ_GET_INFO_BY_FD
https://git.kernel.org/bpf/bpf-next/c/ea2e6467ac36
- [v4,07/12] bpf: Move the signature kfuncs to helpers.c
https://git.kernel.org/bpf/bpf-next/c/8cd189e414bb
- [v4,08/12] bpf: Implement signature verification for BPF programs
(no matching commit)
- [v4,09/12] libbpf: Update light skeleton for signing
(no matching commit)
- [v4,10/12] libbpf: Embed and verify the metadata hash in the loader
(no matching commit)
- [v4,11/12] bpftool: Add support for signing BPF programs
(no matching commit)
- [v4,12/12] selftests/bpf: Enable signature verification for some lskel tests
(no matching commit)
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-09-19 2:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-14 21:51 [PATCH v4 00/12] Signed BPF programs KP Singh
2025-09-14 21:51 ` [PATCH v4 01/12] bpf: Update the bpf_prog_calc_tag to use SHA256 KP Singh
2025-09-19 2:19 ` Alexei Starovoitov
2025-09-21 10:34 ` KP Singh
2025-09-14 21:51 ` [PATCH v4 02/12] bpf: Implement exclusive map creation KP Singh
2025-09-14 21:51 ` [PATCH v4 03/12] libbpf: Implement SHA256 internal helper KP Singh
2025-09-14 21:51 ` [PATCH v4 04/12] libbpf: Support exclusive map creation KP Singh
2025-09-15 19:49 ` Andrii Nakryiko
2025-09-14 21:51 ` [PATCH v4 05/12] selftests/bpf: Add tests for exclusive maps KP Singh
2025-09-14 21:51 ` [PATCH v4 06/12] bpf: Return hashes of maps in BPF_OBJ_GET_INFO_BY_FD KP Singh
2025-09-14 21:51 ` [PATCH v4 07/12] bpf: Move the signature kfuncs to helpers.c KP Singh
2025-09-14 21:51 ` [PATCH v4 08/12] bpf: Implement signature verification for BPF programs KP Singh
2025-09-14 21:51 ` [PATCH v4 09/12] libbpf: Update light skeleton for signing KP Singh
2025-09-14 21:51 ` [PATCH v4 10/12] libbpf: Embed and verify the metadata hash in the loader KP Singh
2025-09-14 21:51 ` [PATCH v4 11/12] bpftool: Add support for signing BPF programs KP Singh
2025-09-18 21:04 ` Quentin Monnet
2025-09-21 10:00 ` KP Singh
2025-09-21 10:04 ` KP Singh
2025-09-21 11:29 ` KP Singh
2025-09-14 21:51 ` [PATCH v4 12/12] selftests/bpf: Enable signature verification for some lskel tests KP Singh
2025-09-19 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=175824841300.3021819.875187543538843071.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bboscaccy@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kpsingh@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.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;
as well as URLs for NNTP newsgroup(s).