STRUCT LANDLOCK_DETAILS(9)

💅 struct landlock_details(9) 💅

okay so bestie, welcome to the Kernel API Manual entry for struct landlock_details — this one's a whole vibe, it's literally just a little receipt of who created a domain. periodt.

---

✨ NAME ✨

struct landlock_details — the domain's creation information, like a birth certificate but for a Landlock domain 🎀

---

🌸 SYNOPSIS 🌸

no cap, here's the whole thing, copy it exactly:

struct landlock_details {
    struct pid *pid;
    uid_t uid;
    char comm[TASK_COMM_LEN];
    char exe_path[];
 };

---

🦋 Members 🦋

• pid — the PID of the task that initially restricted itself, and it still identifies that same task. Keeping a reference to this PID means it will not be recycled. iconic, honestly — no zombie PID shenanigans here.
• uid — the UID of the task that initially restricted itself, captured at creation time. 🫶
• comm — the command line of the task that initially restricted itself, at creation time. It's always NULL terminated. always. 💯
• exe_path — the executable path of the task that initially restricted itself, at creation time. Also always NULL terminated, and never greater than LANDLOCK_PATH_MAX_SIZE. she has limits and she respects them 💅

---

🧚 Description 🧚

This thing is rarely accessed — mainly when you're logging the first domain's denial. lowkey a special-occasion struct, she doesn't come out for just anything 🌈

The contained pointers are initialized at the domain creation time and never changed again. fr fr, they're set once and then they're forever frozen in time — no mutating, no editing, no take-backs. 🎀

---

👑 SEE ALSO 👑

Kernel file ./security/landlock/domain.h, plus these besties:

• struct landlock_hierarchy(9)
• struct landlock_domain(9)
• landlock_union_access_masks(9)

go read them too, iykyk 💖

---

that's the whole page bestie, slay — this one lives in ./security/landlock and it's dated October 2026. mwah, see u in the kernel 🦋✨💜