securityfs_create_dentry(9)

💅 securityfs_create_dentry(9)

okay so bestie, welcome to the Kernel API Manual, section 9 — this is the page for securityfs_create_dentry, and it's lowkey the moment you learn how to make a whole dentry exist in the securityfs filesystem. no cap, very main character of you. ✨

---

🌸 SYNOPSIS 🌸

struct dentry * securityfs_create_dentry (const char *name , umode_t
mode , struct dentry *parent , void *data , const struct file_operations
*fops , const struct inode_operations *iops );

literally copy that exactly, don't @ me, the spacing is part of the vibe (jk it's the signature, but still — exact 🫶).

---

🎀 ARGUMENTS 🎀

• name — a pointer to a string holding the name of the file you wanna create. yes, the actual name-name. 💖
• mode — the permission that the file should have. set it, don't guess it.
• parent — a pointer to the parent dentry for this file. this should be a directory dentry if you set it, obviously. and if this parameter is NULL, then your file gets created in the root of the securityfs filesystem — iconic root placement, no folder drama. 🦋
• data — a pointer to something you (the caller) will want to get back to later on. the fun part: inode.i_private will point to this value on the open call. so it's like leaving yourself a little note and the kernel delivers it. 🙈
• fops — a pointer to a struct file_operations that should be used for this file. this is the whole personality of your file, fr fr.
• iops — a point to a struct of inode_operations that should be used for this file/dir. (yes the original says "a point to" — we're keeping the lore 💀)

---

✨ DESCRIPTION ✨

so this is the basic "create a file/dir/symlink" function for securityfs. it gives you a wide range of flexibility in creating a file, or a directory — tho if you actually want a directory, the securityfs_create_dir function is recommended to be used instead. consider that a friendly nudge, bestie. 🎀

this function returns a pointer to a dentry if it succeeds. and listen — that pointer must be passed to the securityfs_remove function when the file is to be removed. because there is no automatic cleanup that happens if your module is unloaded. you are responsible here. you. not the kernel. you. 😭 that's the whole assignment.

if an error occurs, the function will return the error value (via ERR_PTR). so vibe check that return value, always.

💀 and if securityfs is not enabled in the kernel, the value -ENODEV is returned. that's it, that's the whole mood.

---

👑 SEE ALSO 👑

Kernel file ./security/inode.c — go read it, iykyk — plus these iconic siblings:

• securityfs_create_file(9)
• securityfs_create_dir(9)
• securityfs_create_symlink(9)
• securityfs_remove(9)

---

🌈 SIGN-OFF 🌈

that's the whole page, bestie — brought to you by the source ./security and dated October 2026, living under the securityfs_create_dentry(9) banner the whole time. slay, go create some dentries responsibly, and remember: securityfs_remove is your bestie too. periodt. 💅✨