Documentation: keys: document IDs added since KEY_SPEC_REQKEY_AUTH_KEY

The table of special key IDs stops at KEY_SPEC_REQKEY_AUTH_KEY.
Fill in all the new ones.

Suggested-by: Christian Brauner (Amutable) <brauner@kernel.org>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
Reviewed-by: Christian Brauner (Amutable) <brauner@kernel.org>
Signed-off-by: Andrew Halaney <andrew@amutable.com>
Link: https://patch.msgid.link/20261008-ajhalaney-dmverity-key-identifier-v2-3-008456d189cb@amutable.com
Signed-off-by: Christian Brauner (Amutable) <brauner@kernel.org>
This commit is contained in:
Andrew Halaney 2026-10-08 15:57:37 -05:00 committed by Christian Brauner
parent 5ab0054676
commit bde0f0bcc5
No known key found for this signature in database
GPG Key ID: 91C61BC06578DCA2

View File

@ -372,6 +372,19 @@ process making the call::
KEY_SPEC_GROUP_KEYRING -6 GID-specific keyring
KEY_SPEC_REQKEY_AUTH_KEY -7 assumed request_key()
authorisation key
KEY_SPEC_REQUESTOR_KEYRING -8 request_key() destination
keyring
There are also values that refer to a specific kernel keyring rather than to
anything belonging to the caller. These keyrings are not linked into any
keyring, so a search cannot reach them and the ID is the only way to name
one::
CONSTANT VALUE KEY REFERENCED
============================== ====== ===========================
KEY_SPEC_BPF_KEYRING -9 the ".bpf" keyring
KEY_SPEC_DM_VERITY_KEYRING -10 the ".dm-verity" keyring
KEY_SPEC_FS_VERITY_KEYRING -11 the ".fs-verity" keyring
The main syscalls are: