trace_cap_capable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… trace_cap_capable(9) β€” a Kernel API Manual moment ✨

okay bestie, so this is a page from the Kernel API Manual, and it's about trace_cap_capable β€” literally the little hook that fires right after the kernel has figured out whether a task actually holds a particular effective capability. it's giving "backstage pass to the permission check" energy 🎟️


🌸 NAME 🌸

trace_cap_capable β€” called after it's determined if a task has a particular effective capability πŸ’–


⭐ SYNOPSIS ⭐

void trace_cap_capable (const struct cred *cred , struct user_namespace
*target_ns , const struct user_namespace *capable_ns , int cap , int ret
);

no cap, that's the whole signature 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • cred β€” the credentials being used, iykyk πŸ”‘
  • target_ns β€” the user namespace of the resource that's being accessed 🌐
  • capable_ns β€” the user namespace where the credential actually provides the capability to access the targeted resource. heads up bestie: this one is NULL if ret is not 0 πŸ‘€
  • cap β€” the capability we're checking for πŸ’…
  • ret β€” the return value of the check: 0 if it does, -ve if it does not 😭

πŸ¦‹ DESCRIPTION πŸ¦‹

it lets you trace calls to cap_capable in commoncap.c β€” that's it, that's the whole vibe. main character tracepoint energy πŸ‘‘


πŸ’œ SEE ALSO πŸ’œ

  • Kernel file ./include/trace/events/capability.h πŸ“

and that's the whole page, bestie β€” no crumbs left behind πŸ“

signing off from ./include/trace/events, dated October 2026, page trace_cap_capable(9) β€” slay, go trace some capabilities, periodt πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from