tomoyo_current_namespace(9)

🌸 TOMOYO_CURRENT_NAMESPACE 💅

okay so bestie, welcome to the tomoyo_current_namespace(9) page — it lives in the Kernel API Manual and it is, and I say this with love, a whole little one-trick pony. Let's get into it ✨

---

🎀 NAME 🎀

tomoyo_current_namespace — get ya girl the "struct tomoyo_policy_namespace" for the current thread 🫶

---

🦋 SYNOPSIS 🦋

struct tomoyo_policy_namespace * tomoyo_current_namespace (void );

like that's literally the whole signature, no cap. she takes nothing and gives you a pointer 💖

---

🍓 ARGUMENTS 🍓

• void — no arguments. none. zero. the void is voiding 🙈 nothing to pass in, nothing to worry about, just vibes.

---

✨ DESCRIPTION ✨

so what she does is: she returns a pointer to "struct tomoyo_policy_namespace" for the current thread. that's it. that's the tea ☕

pointer to the policy namespace, for the current thread specifically — like she knows exactly who's asking and hands them their own little namespace pointer. main character energy tbh 👑

no args in, one pointer out. iconic behaviour, honestly 💅

---

🔥 SEE ALSO 🔥

the whole friend group, gathered for your convenience 🫶 go say hi:

• kernel file ./security/tomoyo/common.h
• tomoyo_read_lock(9)
• tomoyo_read_unlock(9)
• tomoyo_sys_getppid(9)
• tomoyo_sys_getpid(9)
• tomoyo_pathcmp(9)
• tomoyo_put_name(9)
• tomoyo_put_condition(9)
• tomoyo_put_group(9)
• tomoyo_task(9)
• tomoyo_same_name_union(9)
• tomoyo_same_number_union(9)
• tomoyo_same_ipaddr_union(9)
• list_for_each_cookie(9)

---

ngl bestie this one is short and sweet — no flags, no exit statuses, no scary caveats. just a pointer and a dream 🌈

---

and that's the page!! mwah 💋 this lil cutie comes to you from ./security/tomoyo, dated October 2026, and she's signing off — stay slay, stay in your own namespace, and don't forget to lock before you read 🧚💜⭐