Linux Kernel Selftest development
 help / color / mirror / Atom feed
* [PATCH v3 4/6] KEYS: Introduce keyring_is_empty()
       [not found] <20261025001105.1824178-1-jarkko@kernel.org>
@ 2026-10-25  0:10 ` Jarkko Sakkinen
  2026-10-26 23:55   ` Eric Biggers
  0 siblings, 1 reply; 3+ messages in thread
From: Jarkko Sakkinen @ 2026-10-25  0:10 UTC (permalink / raw)
  To: David Howells
  Cc: keyrings, Linus Torvalds, Eric Biggers, Jarkko Sakkinen,
	Alasdair Kergon, Mike Snitzer, Mikulas Patocka,
	Benjamin Marzinski, Theodore Y. Ts'o, Thomas Graf, Herbert Xu,
	Andrew Morton, Paul Moore, James Morris, Serge E. Hallyn,
	Shuah Khan, Christian Brauner, open list:DEVICE-MAPPER  (LVM),
	open list,
	open list:FSVERITY: READ-ONLY FILE-BASED AUTHENTICITY PRO...,
	open list:RHASHTABLE, open list:SECURITY SUBSYSTEM,
	open list:KERNEL SELFTEST FRAMEWORK

Introduce keyring_is_empty() in order to decouple for dm-verity and
fs-verity how keyring internally manages the keys.

Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>
---
 drivers/md/dm-verity-verify-sig.c                      |  2 +-
 fs/verity/signature.c                                  |  2 +-
 include/linux/key.h                                    |  1 +
 security/keys/keyring.c                                | 10 ++++++++++
 .../selftests/dm-verity/test-dm-verity-keyring.sh      |  2 +-
 5 files changed, 14 insertions(+), 3 deletions(-)

diff --git a/drivers/md/dm-verity-verify-sig.c b/drivers/md/dm-verity-verify-sig.c
index b2b55c41e2cb..2ccb71bfb3ca 100644
--- a/drivers/md/dm-verity-verify-sig.c
+++ b/drivers/md/dm-verity-verify-sig.c
@@ -153,7 +153,7 @@ int verity_verify_root_hash(const void *root_hash, size_t root_hash_len,
 	if (ret != -ENOKEY && ret != -EKEYREJECTED)
 		return ret;
 
-	if (dm_verity_keyring->keys.nr_leaves_on_tree &&
+	if (!keyring_is_empty(dm_verity_keyring) &&
 	    dm_verity_keyring->restrict_link)
 		ret = verify_pkcs7_signature(root_hash, root_hash_len,
 					     sig_data, sig_len,
diff --git a/fs/verity/signature.c b/fs/verity/signature.c
index 0302a4e506ec..890d33b9d812 100644
--- a/fs/verity/signature.c
+++ b/fs/verity/signature.c
@@ -67,7 +67,7 @@ int fsverity_verify_signature(const struct fsverity_info *vi,
 		return 0;
 	}
 
-	if (fsverity_keyring->keys.nr_leaves_on_tree == 0) {
+	if (keyring_is_empty(fsverity_keyring)) {
 		/*
 		 * The ".fs-verity" keyring is empty, due to builtin signatures
 		 * being supported by the kernel but not actually being used.
diff --git a/include/linux/key.h b/include/linux/key.h
index 3b8af14fb323..df2034fc5436 100644
--- a/include/linux/key.h
+++ b/include/linux/key.h
@@ -439,6 +439,7 @@ extern int restrict_link_reject(struct key *keyring,
 				struct key *restriction_key);
 
 extern int keyring_clear(struct key *keyring);
+bool keyring_is_empty(const struct key *keyring);
 
 extern key_ref_t keyring_search(key_ref_t keyring,
 				struct key_type *type,
diff --git a/security/keys/keyring.c b/security/keys/keyring.c
index 5281da9d5bf7..4642754db6bf 100644
--- a/security/keys/keyring.c
+++ b/security/keys/keyring.c
@@ -443,6 +443,16 @@ static void keyring_destroy(struct key *keyring)
 	assoc_array_destroy(&keyring->keys, &keyring_assoc_array_ops);
 }
 
+/**
+ * keyring_is_empty - Check whether a keyring contains any links
+ * @keyring: The keyring to check.
+ */
+bool keyring_is_empty(const struct key *keyring)
+{
+	return READ_ONCE(keyring->keys.nr_leaves_on_tree) == 0;
+}
+EXPORT_SYMBOL(keyring_is_empty);
+
 /*
  * Describe a keyring for /proc.
  */
diff --git a/tools/testing/selftests/dm-verity/test-dm-verity-keyring.sh b/tools/testing/selftests/dm-verity/test-dm-verity-keyring.sh
index 1f9601ef22f8..792449d356cf 100755
--- a/tools/testing/selftests/dm-verity/test-dm-verity-keyring.sh
+++ b/tools/testing/selftests/dm-verity/test-dm-verity-keyring.sh
@@ -746,7 +746,7 @@ test_keyring_inactive_when_empty() {
     log_info "TEST: Verify dm-verity keyring is inactive when sealed empty"
 
     # When keyring_unsealed=0, the keyring is sealed immediately while empty
-    # This means it should NOT be used for verification (nr_leaves_on_tree=0)
+    # An empty keyring should NOT be used for verification.
 
     log_info "Keyring state (should be empty and sealed):"
     list_keyring_keys
-- 
2.47.3


^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH v3 4/6] KEYS: Introduce keyring_is_empty()
  2026-10-25  0:10 ` [PATCH v3 4/6] KEYS: Introduce keyring_is_empty() Jarkko Sakkinen
@ 2026-10-26 23:55   ` Eric Biggers
  2026-10-27  0:01     ` Jarkko Sakkinen
  0 siblings, 1 reply; 3+ messages in thread
From: Eric Biggers @ 2026-10-26 23:55 UTC (permalink / raw)
  To: Jarkko Sakkinen
  Cc: David Howells, keyrings, Linus Torvalds, Alasdair Kergon,
	Mike Snitzer, Mikulas Patocka, Benjamin Marzinski,
	Theodore Y. Ts'o, Thomas Graf, Herbert Xu, Andrew Morton,
	Paul Moore, James Morris, Serge E. Hallyn, Shuah Khan,
	Christian Brauner, open list:DEVICE-MAPPER (LVM), open list,
	open list:FSVERITY: READ-ONLY FILE-BASED AUTHENTICITY PRO...,
	open list:RHASHTABLE, open list:SECURITY SUBSYSTEM,
	open list:KERNEL SELFTEST FRAMEWORK

On Sun, Oct 25, 2026 at 03:10:12AM +0300, Jarkko Sakkinen wrote:
> +/**
> + * keyring_is_empty - Check whether a keyring contains any links
> + * @keyring: The keyring to check.
> + */

"contains any links" => "contains no links"?  Or even just "is empty".
Otherwise it sounds backwards.

Note that another "is the keyring empty" check just showed up in
mainline in kernel/bpf/keys.c.  So a new version of this patch will be
needed to update that one too.

Otherwise this patch looks good.

- Eric

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH v3 4/6] KEYS: Introduce keyring_is_empty()
  2026-10-26 23:55   ` Eric Biggers
@ 2026-10-27  0:01     ` Jarkko Sakkinen
  0 siblings, 0 replies; 3+ messages in thread
From: Jarkko Sakkinen @ 2026-10-27  0:01 UTC (permalink / raw)
  To: Eric Biggers
  Cc: David Howells, keyrings, Linus Torvalds, Alasdair Kergon,
	Mike Snitzer, Mikulas Patocka, Benjamin Marzinski,
	Theodore Y. Ts'o, Thomas Graf, Herbert Xu, Andrew Morton,
	Paul Moore, James Morris, Serge E. Hallyn, Shuah Khan,
	Christian Brauner, open list:DEVICE-MAPPER (LVM), open list,
	open list:FSVERITY: READ-ONLY FILE-BASED AUTHENTICITY PRO...,
	open list:RHASHTABLE, open list:SECURITY SUBSYSTEM,
	open list:KERNEL SELFTEST FRAMEWORK

On Mon, Oct 26, 2026 at 04:55:28PM -0700, Eric Biggers wrote:
> On Sun, Oct 25, 2026 at 03:10:12AM +0300, Jarkko Sakkinen wrote:
> > +/**
> > + * keyring_is_empty - Check whether a keyring contains any links
> > + * @keyring: The keyring to check.
> > + */
> 
> "contains any links" => "contains no links"?  Or even just "is empty".
> Otherwise it sounds backwards.
> 
> Note that another "is the keyring empty" check just showed up in
> mainline in kernel/bpf/keys.c.  So a new version of this patch will be
> needed to update that one too.
> 
> Otherwise this patch looks good.

I'll fix that up. Related, bpf_keyring_lookup() also needs to be
addressed now that I have it in my tree. 

> 
> - Eric

Br, Jarkko

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-10-27  0:01 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <20261025001105.1824178-1-jarkko@kernel.org>
2026-10-25  0:10 ` [PATCH v3 4/6] KEYS: Introduce keyring_is_empty() Jarkko Sakkinen
2026-10-26 23:55   ` Eric Biggers
2026-10-27  0:01     ` Jarkko Sakkinen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox