aa_current_raw_label(9)
π aa_current_raw_label(9)
okay so bestie, real talk β this is a kernel API manual page for aa_current_raw_label, and honestly? she's lowkey iconic. AppArmor vibes only. Let's get into it π
β¨ NAME β¨
aa_current_raw_label β bestie's whole job is finding the current task's confining label π¦
πΈ SYNOPSIS πΈ
struct aa_label * aa_current_raw_label (void );
like, she takes nothing and gives you a struct aa_label * back. main character energy fr fr π
π ARGUMENTS π
voidβ no arguments, periodt. she doesn't want your input, she's booked and busy π
β RETURN β
You get back either an up-to-date confining label or the ns unconfined label β and the manual is very clear about this, so listen up: it's NOT NULL. never. not once. not ever. NOT NULL no cap πβ¨
π«Ά DESCRIPTION π«Ά
so the way that this fn works? she will not update the task's cred to the most up-to-date version of the label. that sounds like a downside but bestie it's literally the whole point β because she doesn't touch the cred, it is safe to call when inside of locks ππ
that's it. that's the tea. call her from inside a lock, she won't betray you π§
ngl the "won't update the cred" thing is a feature, not a bug β the original page says it plainly, so don't come for me π₯
π SEE ALSO π
- Kernel file
./security/apparmor/include/cred.hπ aa_get_newest_cred_label(9)aa_get_current_label(9)__end_cred_crit_section(9)__begin_cred_crit_section(9)__end_current_label_crit_section(9)end_current_label_crit_section(9)__begin_current_label_crit_section(9)begin_current_label_crit_section(9)
go read the whole crit section family, they're all serving ππ
kisses bestie, this page lives in ./security/apparmor/include and she's dated October 2026 β go off, my little kernel gremlin ππ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms