From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Christian Brauner <brauner@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL for v7.4] vfs keyring
Date: Mon, 26 Oct 2026 10:10:54 -0400 [thread overview]
Message-ID: <61898b2b9de5e6be98c7b8e462ba29595cae3e26.camel@HansenPartnership.com> (raw)
In-Reply-To: <20261024-vfs-7.4-rc1.keyring-db88a8f3b5b1@brauner>
On Sat, 2026-10-24 at 12:44 +0200, Christian Brauner wrote:
> Hey Linus,
>
> This is a delayed pull request which was waiting for the bpf merge.
> This used a shared branch.
>
> /* Summary */
> This adds well-known key ids for the .dm-verity and .fs-verity
> keyrings.
>
> Neither keyring is linked into any other keyring so request_key() and
> KEYCTL_SEARCH can't find them. Userspace has to scrape the serial out
> of /proc/keys before it can add a key to either of them. That's not
> great as any user can add a key with a newline in its description and
> make /proc/keys show a fake .dm-verity keyring line with whatever
> serial they like.
>
> /* Testing */
>
> No build failures or warnings were observed.
>
> /* Conflicts */
>
> Merge conflicts with mainline
> =============================
>
> No known conflicts.
>
> Merge conflicts with other trees
> ================================
>
> No known conflicts.
>
> The following changes since commit
> 1b7415bf70be95b9a1e7e87d544867881065613f:
>
> Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf 7.3-rc2
> (2026-09-06 16:17:40 -0700)
>
> are available in the Git repository at:
>
> git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-
> 7.4-rc1.keyring
>
> for you to fetch changes up to
> 503b65da9a7e5447d91222f62399522f2f62a0fa:
>
> Merge patch series "keys: Add well known IDs for fs-verity/dm-
> verity keys" (2026-10-12 23:37:42 +0200)
>
> ----------------------------------------------------------------
> vfs-7.4-rc1.keyring
>
> Please consider pulling these changes from the signed vfs-7.4-
> rc1.keyring tag.
>
> Thanks!
> Christian
>
> ----------------------------------------------------------------
> Andrew Halaney (3):
> keys: add KEY_SPEC_DM_VERITY_KEYRING
> keys: add KEY_SPEC_FS_VERITY_KEYRING
> Documentation: keys: document IDs added since
> KEY_SPEC_REQKEY_AUTH_KEY
It would actually have been nice to copy the keyrings list and
maintainers on this. I don't think there's an objection but not cc'ing
the list and maintainers makes it look like some type of end run.
> Christian Brauner (2):
> Merge bpf keyring work from of
> git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next
> Merge patch series "keys: Add well known IDs for fs-verity/dm-
> verity keys"
This is a bit nasty because the keyring specs get renumbered inside the
merges ... it would have been much clearer to people looking at the
history if the patches were rebased instead.
Regards,
James
next prev parent reply other threads:[~2026-10-26 14:10 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 10:13 [GIT PULL 00/19 for v7.4] v7.4 Christian Brauner
2026-10-16 10:14 ` [GIT PULL 01/19 for v7.4] ipc misc Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:15 ` [GIT PULL 02/19 for v7.4] kernel signal Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:15 ` [GIT PULL 03/19 for v7.4] namespace misc Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:16 ` [GIT PULL 04/19 for v7.4] vfs bfs Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:16 ` [GIT PULL 05/19 for v7.4] vfs bh Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:16 ` [GIT PULL 06/19 for v7.4] vfs binfmt Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:17 ` [GIT PULL 07/19 for v7.4] vfs close_range Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:18 ` [GIT PULL 08/19 for v7.4] vfs coredump Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:18 ` [GIT PULL 09/19 for v7.4] vfs file Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:19 ` [GIT PULL 10/19 for v7.4] vfs idmap Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:21 ` [GIT PULL 11/19 for v7.4] vfs iomap Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:21 ` [GIT PULL 12/19 for v7.4] vfs kernfs Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:22 ` [GIT PULL 13/19 for v7.4] vfs lookup Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:23 ` [GIT PULL 14/19 for v7.4] vfs misc Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:24 ` [GIT PULL 15/19 for v7.4] vfs mount Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:25 ` [GIT PULL 16/19 for v7.4] vfs netfs Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:26 ` [GIT PULL 17/19 for v7.4] vfs shared net-next pidfd Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:26 ` [GIT PULL 18/19 for v7.4] vfs shared super Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-16 10:27 ` [GIT PULL 19/19 for v7.4] vfs sync_close Christian Brauner
2026-10-20 7:12 ` pr-tracker-bot
2026-10-24 10:44 ` [GIT PULL for v7.4] vfs keyring Christian Brauner
2026-10-26 2:35 ` Linus Torvalds
2026-10-26 8:19 ` Christian Brauner
2026-10-26 14:10 ` James Bottomley [this message]
2026-10-26 20:35 ` 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=61898b2b9de5e6be98c7b8e462ba29595cae3e26.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®