landlock_init_hierarchy_log(9)

💅 landlock_init_hierarchy_log(9) — like, the Kernel API Manual, bestie ✨

Okay so real quick: we're in the <pink>Kernel API Manual</pink> today and the star of the show is <rainbow>landlock_init_hierarchy_log 🎀 she does a partial init of a landlock_hierarchy and honestly? iconic behaviour.

---

✨ NAME ✨

landlock_init_hierarchy_log — partially initialize landlock_hierarchy 🦋 (yes, partially, she's not doing the whole thing, read the room)

---

🌸 SYNOPSIS 🌸

int landlock_init_hierarchy_log (struct landlock_hierarchy *const
       hierarchy );

---

🎀 ARGUMENTS 🎀

• hierarchy — the hierarchy you're gonna initialize, bestie 💖 that's literally it, that's the whole argument.

---

💅 DESCRIPTION 💅

So here's the vibe check 👑: the <purple>current task</purple> gets referenced as the domain that is enforcing the restriction. That's the whole point, iykyk.

⚠️ Okay this part matters and I'm not gonna sugarcoat it: the <red>subjective credentials must not be in an overridden state</red>. Like, fr fr, do not do that. 🫶

Also, heads up — hierarchy->parent and hierarchy->usage should already be set before you come through here. She's not setting those, she's assuming you handled it. Not me doing your homework for you 💀

---

🌈 RETURN 🌈

• <green>0</green> on success — slay ✨
• -errno on failure — and that's the whole mood 😭

---

⭐ SEE ALSO ⭐

Kernel file ./security/landlock/domain.c, plus the whole friend group:

• landlock_unmask_layers(9)
• landlock_init_layer_masks(9)
• landlock_merge_ruleset(9)
• get_current_exe(9)
• landlock_get_quiet_optional_accesses(9)

---

k byeee 🧚 this page lives in <pink>./security/landlock</pink>, dated October 2026, and it's signed <rainbow>landlock_init_hierarchy_log(9) — periodt 💜✨