eventfs_create_events_dir(9)

💅 eventfs_create_events_dir — bestie, let's build the top-level events dir

okay so this is from the Kernel API Manual, and it's literally the function that creates the top level events directory. yes bestie, that directory. the big one. the main character. 👑

---

✨ SYNOPSIS ✨

struct eventfs_inode * eventfs_create_events_dir (const char *name ,
struct dentry *parent , const struct eventfs_entry *entries , int size ,
void *data );

notice how it hands you back a struct eventfs_inode *? yeah. it's giving "i made you something and it's an inode". 🎀

---

🌸 ARGUMENTS 🌸

• name — the name of the top level directory you're creating. like, what are we calling this thing, bestie? 🏷️
• parent — the parent dentry for this file, over there in the tracefs directory. that's its home. that's where it lives. 🏠
• entries — a list of entries that represent the files under this directory. the whole squad of files, listed out. 💖
• size — the number of entries. so like, how many of them there are. count them. go off. 🔢
• data — the default data to pass to the files. and yes, lowkey, an entry may override it. so it's a default default. 🙈

---

🦋 DESCRIPTION 🦋

fr fr, what this function does is create the top of the trace event directory. that's it, that's the vibe. ✨

and if you wanna know about how entries actually gets used? see eventfs_create_dir. it's all there, iykyk. 👀

side note bestie: nothing here is deprecated or dangerous, so you can absolutely slay responsibly. 💅

---

🌈 SEE ALSO 🌈

Kernel file ./fs/tracefs/event_inode.c — plus the whole friend group:

• lookup_file(9)
• lookup_dir_entry(9)
• eventfs_d_release(9)
• lookup_file_dentry(9)
• eventfs_root_lookup(9)
• eventfs_create_dir(9)
• eventfs_remove_rec(9)
• eventfs_remove_dir(9)
• eventfs_remove_events_dir(9)

---

and that's the whole page, bestie 🫶 this one came out of ./fs/tracefs, dated October 2026, and it's eventfs_create_events_dir(9) — periodt. 💜