From: Christian Brauner <brauner@kernel.org>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
Benjamin Marzinski <bmarzins@redhat.com>,
David Howells <dhowells@redhat.com>,
Jarkko Sakkinen <jarkko@kernel.org>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Eric Biggers <ebiggers@kernel.org>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
Andrew Halaney <andrew@amutable.com>,
dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
bpf@vger.kernel.org, fsverity@lists.linux.dev,
linux-doc@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 0/3] keys: Add well known IDs for fs-verity/dm-verity keys
Date: Fri, 16 Oct 2026 10:27:19 +0200 [thread overview]
Message-ID: <20261016-ratlos-endkunde-eindimensional-1fe5eef08d13@brauner> (raw)
In-Reply-To: <DM5UD20248FG.3BXPS76LK06F5@gmail.com>
On Fri, Oct 16, 2026 at 12:38:11AM +0000, Alexei Starovoitov wrote:
> On Mon, Oct 12, 2026 at 12:38 PM Christian Brauner <brauner@kernel.org> wrote:
> > Applied to the vfs-7.4.keyring branch of the vfs/vfs.git tree.
> > Patches in the vfs-7.4.keyring branch should appear in linux-next soon.
>
> What is this branch based on ?
> v2 was sent against bpf-next, because
> commit 264d8fd2794f ("bpf, keys: Add a bpf keyring for program signature validation")
> is only there.
> All hunks in keyctl.h, key.h and process_keys.c have its lines as
> context, so the patches don't apply to -rc as-is.
> And patch 3 documents KEY_SPEC_BPF_KEYRING.
It's based on the portion of bpf-next that has Daniel's keyring patches.
Which means I just wait until bpf-next is merged and then send it as a
follow-up pr.
prev parent reply other threads:[~2026-10-16 8:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-08 20:57 [PATCH bpf-next v2 0/3] keys: Add well known IDs for fs-verity/dm-verity keys Andrew Halaney
2026-10-08 20:57 ` [PATCH bpf-next v2 1/3] keys: add KEY_SPEC_DM_VERITY_KEYRING Andrew Halaney
2026-10-08 21:44 ` bot+bpf-ci
2026-10-08 21:57 ` Andrew Halaney
2026-10-11 9:35 ` Manuel Huber
2026-10-12 13:12 ` Christian Brauner
2026-10-12 17:14 ` Manuel Huber
2026-10-08 20:57 ` [PATCH bpf-next v2 2/3] keys: add KEY_SPEC_FS_VERITY_KEYRING Andrew Halaney
2026-10-08 20:57 ` [PATCH bpf-next v2 3/3] Documentation: keys: document IDs added since KEY_SPEC_REQKEY_AUTH_KEY Andrew Halaney
2026-10-12 10:38 ` [PATCH bpf-next v2 0/3] keys: Add well known IDs for fs-verity/dm-verity keys Christian Brauner
2026-10-16 0:38 ` Alexei Starovoitov
2026-10-16 8:27 ` Christian Brauner [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=20261016-ratlos-endkunde-eindimensional-1fe5eef08d13@brauner \
--to=brauner@kernel.org \
--cc=agk@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrew@amutable.com \
--cc=andrii@kernel.org \
--cc=bmarzins@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=dhowells@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=fsverity@lists.linux.dev \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=paul@paul-moore.com \
--cc=rdunlap@infradead.org \
--cc=serge@hallyn.com \
--cc=skhan@linuxfoundation.org \
--cc=snitzer@kernel.org \
--cc=tytso@mit.edu \
/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