request_key_tag(9)

request_key_tag 🎀

okay bestie, welcome to the Kernel API Manual page for request_key_tag ✨ it’s giving “request a key and wait for construction,” and honestly? iconic. let’s get into it.

💖 NAME 💖

request_key_tag — Request a key and wait for construction.

✨ SYNOPSIS ✨

struct key * request_key_tag (struct key_type *type , const char
       *description , struct key_tag *domain_tag , const char *callout_info );

🎀 ARGUMENTS 🎀

• type — the type of key. like, what kind of key are we even dealing with, bestie?
• description — the searchable description of the key. yes, searchable. periodt.
• domain_tag — the domain in which the key operates. domain vibes, got it.
• callout_info — the data to pass to the instantiation upcall (or NULL). if there’s no data, it’s NULL, no cap.

🦋 DESCRIPTION 🦋

okay so this works as for request_key_and_link, except for a few very important details:

• it does not add the returned key to a keyring if found. no sneaky keyring add, bestie.
• new keys are always allocated in the user’s quota. yes, always.
• the callout_info must be a NUL-terminated string. literal must.
• no auxiliary data can be passed. none, zero, zilch.

furthermore, it then works as wait_for_key_construction to wait for the completion of keys undergoing construction with a non-interruptible wait. so it’s gonna wait, and that wait is non-interruptible — keep that in mind 💅

🌈 SEE ALSO 🌈

• Kernel file ./security/keys/request_key.c
• complete_request_key(9)
• request_key_and_link(9)
• wait_for_key_construction(9)
• request_key_with_auxdata(9)
• request_key_rcu(9)

mwah 💋 that’s the page! source path is ./security/keys, the date is October 2026, and the page is request_key_tag(9) — love that for us 🫶✨