Re: [PATCH bpf-next v2 0/3] keys: Add well known IDs for fs-verity/dm-verity keys

[Christian Brauner]

On Fri, Oct 16, 2026 at 02:53:23PM +0000, Alexei Starovoitov wrote:
> On Fri Oct 16, 2026 at 8:27 AM UTC, Christian Brauner wrote:
> > 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@xxxxxxxxxx> 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.
> 
> ohh. that should work. If it's simpler I can take this patch set into bpf-next,
> so you wouldn't need to monitor merge window that closely.

LLMs make that kinda trivial. I need to send late merge window PRs a lot
when we e.g., do tree-wide changes that would cause a lot of merge
conflicts if constantly carried in -next.