generic_ci_..._strict_name(9)

💅 generic_ci_..._strict_name(9) — like, the vibe check for filenames

okay bestie, welcome to the Kernel API Manual entry for generic_ci_..._strict_name(9). yes the name is a whole mouthful, no i will not be shortening it, it's iconic in its own chaotic way. sit down, grab a strawberry drink 🍓, and let's get into it.

---

✨ NAME ✨

generic_ci_validate_strict_name — the function that checks whether a name is even allowed to become a directory entry. it's giving bouncer at the club door fr fr 🫶

---

🎀 SYNOPSIS 🎀

bool generic_ci_validate_strict_name (struct inode *dir , const struct qstr *name );

---

🦋 ARGUMENTS 🦋

• dir — the inode of the directory where the new file is gonna be created. like, the parent folder, the one holding the door open 💖
• name — the name of the new file. the little guy whose fate we're judging ✨

---

🌸 DESCRIPTION 🌸

so what does this function actually do? it checks if the proposed filename is valid for the parent directory. that's the whole job. main character energy, honestly.

what that means in practice: only valid UTF-8 filenames will be accepted for casefold directories from filesystems that were created with the strict encoding flag. so if the directory is strict about encoding, the name better be valid UTF-8 or it's not getting in 😭

but also — and this is the lowkey important part — any name will be accepted for directories that don't have casefold enabled, or that aren't being strict with the encoding. so no-cap, the strictness is conditional, it's not out here gatekeeping everything 💅

---

👑 RETURN 👑

• True — the filename is suitable for this directory. and yes, it can return true even if a given name isn't suitable for a strict encoding directory, as long as the directory being used isn't strict. plot twist, i know 🙈
• False — the filename isn't suitable for this directory. this only happens when a directory is casefolded and the filesystem is strict about its encoding. the stars really gotta align for a false, ngl ⭐

---

🌈 SEE ALSO 🌈

Kernel file ./include/linux/fs.h plus the whole extended friend group:

• enum positive_aop_returns(9)
• struct address_space(9)
• struct file_ra_state(9)
• struct file(9)
• i_uid_into_vfsuid(9)
• i_uid_needs_update(9)
• i_uid_update(9)
• i_gid_into_vfsgid(9)
• i_gid_needs_update(9)
• i_gid_update(9)
• inode_fsuid_set(9)
• inode_fsgid_set(9)
• fsuidgid_has_mapping(9)
• inode_set_ctime(9)
• file_write_started(9)
• file_write_not_started(9)
• struct renamedata(9)
• is_mgtime(9)
• iput_if_not_last(9)
• is_idmapped_mnt(9)
• file_start_write(9)
• file_end_write(9)
• kiocb_start_write(9)
• kiocb_end_write(9)
• name_is_dot_dotdot(9)
• name_contains_dotdot(9)
• inode_dio_begin(9)
• inode_dio_end(9)

---

okay that's the whole page, you ate that 🍽️✨ this little beauty lives over in ./include/linux and it's dated October 2026 — so yes, it's a future icon, we been knew 💜🎀 bye bestie, go validate some names responsibly 💅