has_ns_capability(9)

🎀 has_ns_capability(9) 🎀

okay so bestie, welcome to the Kernel API Manual entry for has_ns_capability — yes, the (9) is doing its little kernel-doc thing. This is literally the vibe check for whether a task has a capability in a specific user namespace. Let's get into it. 💅

✨ NAME ✨

has_ns_capability — Does a task have a capability in a specific user ns

🌸 SYNOPSIS 🌸

bool has_ns_capability (struct task_struct *t , struct user_namespace
*ns , int cap );

🦋 ARGUMENTS 🦋

• t — the task in question, like the main-character task you're checking on 👑
• ns — target user namespace, literally the namespace we're asking about
• cap — the capability to be tested for, aka the specific cap on trial 🔥

💖 DESCRIPTION 💖

It returns true if the specified task has the given superior capability currently in effect to the specified user namespace, and false if not. That's the whole vibe: task + namespace + capability, does it have it, yes or no.

⚠️ Important little note, bestie: this does not set PF_SUPERPRIV on the task. Nope. Not even a little. So don't expect that flag to get cute and appear. 😭

🌈 SEE ALSO 🌈

Kernel file ./kernel/capability.c — plus the whole friend group:

• sys_capget(9)
• sys_capset(9)
• has_ns_capability_noaudit(9)
• has_capability_noaudit(9)
• ns_capable(9)
• ns_capable_noaudit(9)
• ns_capable_setid(9)
• capable(9)
• capable_noaudit(9)
• file_ns_capable(9)
• privileged_wrt_inode_uidgid(9)
• capable_wrt_inode_uidgid(9)
• ptracer_capable(9)

mwah 💋 that's the whole page, bestie. This little icon comes from source/version ./kernel, dated October 2026, and it's literally has_ns_capability(9) — periodt. 🫶💖