key_revoke(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… key_revoke(9) β€” like, the kernel API manual bestie ✨

okay so this is a page from the Kernel API Manual (key_revoke(9)) and honestly it's a short one but it eats. let's get into it 🫢


🌸 NAME 🌸

key_revoke β€” revoke a key. that's it. that's the whole vibe. πŸ’…


✨ SYNOPSIS ✨

void key_revoke (struct key *key );

no return value, no drama, it just does the thing. iconic behavior honestly πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • key β€” the key you're revoking. the one getting yeeted. the main character of this whole operation πŸ¦‹

πŸ’– DESCRIPTION πŸ’–

okay so here's what's actually happening, bestie. key_revoke marks a key as being revoked and then asks the type to free up its resources. so it's like, "hey, this key is done for ✌️" and then it hands off the cleanup to whoever knows how to clean up that type. teamwork, no cap 🀝

and then β€” and this is the part you gotta remember β€” the revocation timeout is set, and the key and all its links will be automatically garbage collected after key_gc_delay amount of time, if they're not manually dealt with first.

read that again bestie. key_gc_delay. automatic garbage collection. the key AND all its links. if nobody deals with them manually, the kernel will do it for them. so like, you can do it yourself, but the timer is ticking the whole time 🌈⏳

πŸ¦‹ SEE ALSO πŸ¦‹

all the siblings, in the kernel file ./security/keys/key.c:

the whole friend group fr fr πŸ’œ


πŸ’« and that's the page!! brought to you by ./security/keys, dated October 2026, and it's giving kernel security realness. go revoke responsibly, bestie. mwah πŸ“βœ¨
πŸ“¦ where this page comes from