From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: memxor@gmail.com, brauner@kernel.org, kpsingh@kernel.org,
ast@kernel.org, john.fastabend@gmail.com,
a.s.protopopov@gmail.com, bpf@vger.kernel.org,
dhowells@redhat.com, jarkko@kernel.org, keyrings@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 00/11] BPF keyring and signed loader ML-DSA support
Date: Sun, 30 Aug 2026 01:20:56 +0000 [thread overview]
Message-ID: <178805285688.3192144.16351453392396630478.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260828175227.1537793-1-daniel@iogearbox.net>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Fri, 28 Aug 2026 19:52:16 +0200 you wrote:
> Add a dedicated BPF keyring which is integrated for BPF signing. It
> is modelled after the dm-verity keyring which was added in commit
> 033724b ("dm-verity: add dm-verity keyring") and which can eventually
> be used also via systemd through the same enrollment method as in
> dm-verity's case. It is selected with a new well-known keyring_id
> VERIFY_USE_BPF_KEYRING and gives an operator a place to enroll a
> BPF-only signing key at boot, specifically scoped to signed BPF
> program loading. Next, to demonstrate that BPF signing is algorithm
> agnostic, we add a few small tooling changes to support ML-DSA and
> integrate everything into BPF selftest for BPF CI to ensure nothing
> breaks with future changes. For more details, see individual commits.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,01/11] bpf, keys: Add a bpf keyring for program signature validation
https://git.kernel.org/bpf/bpf-next/c/264d8fd2794f
- [bpf-next,v4,02/11] bpf: Refuse caller-supplied keyrings when the bpf one is active
https://git.kernel.org/bpf/bpf-next/c/abaa0835b4f3
- [bpf-next,v4,03/11] bpf: Raise the bound on a program's signature size
https://git.kernel.org/bpf/bpf-next/c/300b348e6d5e
- [bpf-next,v4,04/11] bpftool: Support ML-DSA program signing
https://git.kernel.org/bpf/bpf-next/c/d37168c99361
- [bpf-next,v4,05/11] selftests/bpf: Add a test for the sealed bpf keyring
https://git.kernel.org/bpf/bpf-next/c/6754aeca6022
- [bpf-next,v4,06/11] selftests/bpf: Rebuild signed lskels when signing key changes
https://git.kernel.org/bpf/bpf-next/c/e7ada0800ce2
- [bpf-next,v4,07/11] selftests/bpf: Rename the verify_sig_setup.sh setup into setup-rsa
https://git.kernel.org/bpf/bpf-next/c/1841d6cbc5c7
- [bpf-next,v4,08/11] selftests/bpf: Add an end-to-end ML-DSA signed loader test
https://git.kernel.org/bpf/bpf-next/c/478cf384def8
- [bpf-next,v4,09/11] selftests/bpf: Allow appending to guest kernel cmdline in vmtest.sh
https://git.kernel.org/bpf/bpf-next/c/b638a82d64f1
- [bpf-next,v4,10/11] selftests/bpf: Add tests for bpf keyring in signed loader
https://git.kernel.org/bpf/bpf-next/c/1c8cb8bf7329
- [bpf-next,v4,11/11] Documentation/bpf: Document the bpf keyring and improve examples
https://git.kernel.org/bpf/bpf-next/c/8588fa592985
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-08-30 1:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 17:52 [PATCH bpf-next v4 00/11] BPF keyring and signed loader ML-DSA support Daniel Borkmann
2026-08-28 17:52 ` [PATCH bpf-next v4 01/11] bpf, keys: Add a bpf keyring for program signature validation Daniel Borkmann
2026-08-28 19:06 ` bot+bpf-ci
2026-08-31 10:05 ` Christian Brauner
2026-08-28 17:52 ` [PATCH bpf-next v4 02/11] bpf: Refuse caller-supplied keyrings when the bpf one is active Daniel Borkmann
2026-08-31 10:05 ` Christian Brauner
2026-08-28 17:52 ` [PATCH bpf-next v4 03/11] bpf: Raise the bound on a program's signature size Daniel Borkmann
2026-08-28 17:52 ` [PATCH bpf-next v4 04/11] bpftool: Support ML-DSA program signing Daniel Borkmann
2026-08-28 17:52 ` [PATCH bpf-next v4 05/11] selftests/bpf: Add a test for the sealed bpf keyring Daniel Borkmann
2026-08-28 18:53 ` bot+bpf-ci
2026-08-28 17:52 ` [PATCH bpf-next v4 06/11] selftests/bpf: Rebuild signed lskels when signing key changes Daniel Borkmann
2026-08-28 17:52 ` [PATCH bpf-next v4 07/11] selftests/bpf: Rename the verify_sig_setup.sh setup into setup-rsa Daniel Borkmann
2026-08-28 17:52 ` [PATCH bpf-next v4 08/11] selftests/bpf: Add an end-to-end ML-DSA signed loader test Daniel Borkmann
2026-08-28 18:53 ` bot+bpf-ci
2026-08-28 17:52 ` [PATCH bpf-next v4 09/11] selftests/bpf: Allow appending to guest kernel cmdline in vmtest.sh Daniel Borkmann
2026-08-28 17:52 ` [PATCH bpf-next v4 10/11] selftests/bpf: Add tests for bpf keyring in signed loader Daniel Borkmann
2026-08-28 18:53 ` bot+bpf-ci
2026-08-28 17:52 ` [PATCH bpf-next v4 11/11] Documentation/bpf: Document the bpf keyring and improve examples Daniel Borkmann
2026-08-28 18:53 ` bot+bpf-ci
2026-08-30 1:20 ` patchwork-bot+netdevbpf [this message]
2026-08-31 10:05 ` [PATCH bpf-next v4 00/11] BPF keyring and signed loader ML-DSA support Christian Brauner
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=178805285688.3192144.16351453392396630478.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=a.s.protopopov@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=dhowells@redhat.com \
--cc=jarkko@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=keyrings@vger.kernel.org \
--cc=kpsingh@kernel.org \
--cc=memxor@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