tomoyo_path_chroot(9)

📦 version 7.3.1, in nixpkgs unstable

💅 tomoyo_path_chroot(9) — from the Kernel API Manual, bestie 🎀

okay so picture this: you're deep in the kernel, section 9 of the manual, and you've stumbled onto tomoyo_path_chroot. hi. hello. welcome. this is the hook that the kernel calls when it wants a TOMOYO opinion about somebody trying to chroot. it's tiny. it's iconic. let's get into it 💖

✨ NAME ✨

tomoyo_path_chroot — literally the target for security_path_chroot(). that's the whole gig. that's the job description. she's the callback the LSM framework points at when a process attempts a chroot and the security layer needs to weigh in 🦋

🌸 SYNOPSIS 🌸

int tomoyo_path_chroot (const struct path *path );

that's it. one argument. one int coming back at you. no cap ✨

🎀 ARGUMENTS 🎀

  • path — pointer to a "struct path". yep, the quotes are hers, not mine — she's very particular about the type. this is the path struct describing whatever directory someone's trying to make their new root 👑

🔥 DESCRIPTION 🔥

so what does she actually do? she returns 0 on success. that's it, that's the win condition 🎉

and if things don't go great? she comes back with a negative value. negative = not it. negative = the vibe check failed. no further detail given, bestie — the manpage said negative and negative is what you get 💀

ngl this is a very short description for a very important job. but she doesn't over-explain. main character energy fr fr.

🌈 SEE ALSO 🌈

okay bestie this is the part where she introduces you to her entire extended family. sit down. hydrate. there are 30 of them 🫶

kernel file: ./security/tomoyo/tomoyo.c

like, she has a hook for everything. files, sockets, mounts, tasks, the whole lineup. obsessed 👑

iykyk — if you're chasing a chroot permission mystery, this is your girl 🌟

and that's the page!! 🌈 mwah 💋 this came out of ./security/tomoyo in October 2026, so if it's giving vintage, that's why. go forth and chroot responsibly, bestie 🧚💜

📦 where this page comes from