aa_audit(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… aa_audit(9) β€” bestie's guide to the Kernel API Manual ✨

okay so picture this: you're deep in the kernel, AppArmor is doing its thing, and something audit-worthy just happened. This little function is the one that logs it πŸŽ€


🌸 NAME 🌸

aa_audit β€” literally logs a profile based audit event straight to the audit subsystem. no cap, that's the whole job πŸ’–


✨ SYNOPSIS ✨

int aa_audit (int type , struct aa_profile *profile , struct apparmor_audit_data *ad , void (*cb) (struct audit_buffer *, void *) );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • type β€” the audit type for the message. it's giving "what kind of event is this" energy 🏷️
  • profile β€” the profile you're checking against. this one is NOT NULL, so don't even try it πŸ™ˆ
  • ad β€” the audit event itself. also NOT NULL, bestie, these two are non-negotiable βœ‹
  • cb β€” an optional callback fn for the type specific fields. MAYBE NULL β€” it's giving flexible queen πŸ‘‘

🌈 DESCRIPTION 🌈

handles the default message switching based off of the audit mode flags ✨ so like, depending on which flags are set, the message gets built differently β€” and this function is the main character doing that switching 🫢


πŸ”₯ RETURN πŸ”₯

returns an error on failure. that's it, that's the tea πŸ’€


πŸ‘‘ SEE ALSO πŸ‘‘


aaaand that's a wrap, bestie 🧚 from ./security/apparmor, in the very iconic month of October 2026 β€” this page is aa_audit(9), and honestly? she ate πŸ’…β­πŸ“

πŸ“¦ where this page comes from