unpack_strs_table(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… unpack_strs_table(9) β€” from the Kernel API Manual, bestie

okay so picture this: it's a unpack_strs_table(9) moment. this little icon is literally out here unpacking a profile transition table and honestly? it's giving main character energy in ./security/apparmor/policy_unpack.c. πŸŽ€


✨ NAME ✨

unpack_strs_table β€” unpack a profile transition table πŸ¦‹


🌸 SYNOPSIS 🌸

int unpack_strs_table (struct aa_ext *e , const char *name , bool multi
, struct aa_str_table *strs );

like, that's the whole vibe. four args, one int coming back at you. no cap. ✨


πŸ’– ARGUMENTS πŸ’–

  • e β€” the serialized data extent information. this one is NOT NULL, so do not even think about passing a null bestie, i'm serious πŸ™ˆ
  • name β€” the name of the table. and guess what, this one MAY BE NULL, so it's the chill one of the group πŸ’…
  • multi β€” allow multiple strings on a single entry. yes queen, let them stack πŸ”₯
  • strs β€” the str table to unpack to. also NOT NULL! same rules, no nulls, we don't do that here 😭

⭐ RETURN ⭐

0 if the table successfully unpacked or wasn't present at all (we love a low-stakes absence πŸ’œ). otherwise you get an error. periodt.

ngl, "not present" counting as a success is such a mood β€” no table, no problem, still 0. 🧚

🌈 SEE ALSO 🌈

okay so here's the whole friend group, all of them from the kernel file ./security/apparmor/policy_unpack.c:

go read them, iykyk 🫢


and that's the page!! brought to you by ./security/apparmor, dated October 2026 β€” mwah, slay, see you in the next manpage πŸ’…βœ¨

πŸ“¦ where this page comes from