nilfs_ifile_create_inode(9)

🦋 nilfs_ifile_create_inode(9) — the "make a new disk inode" girlie 🎀

okay so this is a kernel API manual page, and yes bestie, we're in nilfs_ifile_create_inode(9) territory — section 9, kernel-space, very demure, very minding-my-own-business-in-the-filesystem. ✨

---

💖 NAME 💖

nilfs_ifile_create_inode — literally just create a new disk inode. that's the whole vibe. 🫶

---

🌸 SYNOPSIS 🌸

int nilfs_ifile_create_inode (struct inode *ifile , u64 *out_ino ,
struct buffer_head **out_bh );

like… she takes three things and gives you back an int. iconic behavior honestly. 👑

---

✨ ARGUMENTS ✨

• ifile — the ifile inode. that's your main character right there, she's the metadata file doing all the work 💅
• out_ino — a pointer to a variable where the inode number gets stored. your little souvenir 🎀
• out_bh — a buffer_head that contains the newly allocated disk inode. yes, the whole buffer, no she's not doing halves 🦋

---

💜 DESCRIPTION 💜

so nilfs_ifile_create_inode allocates a new inode in the ifile metadata file — and then it does two whole things for you, because she's an overachiever:

• it stores the inode number in the variable pointed to by out_ino ⭐
• and it stores the ifile's buffer with the disk inode in the location pointed to by out_bh 💖

that's it. that's the function. no cap, she's efficient. 🌈

---

🔥 RETURN 🔥

returns 0 on success, or one of these negative error codes if things go sideways (and not in the cute way 😭):

• -EIO — I/O error (including metadata corruption 💀). yeah, corruption. we don't love that.
• -ENOMEM — insufficient memory available. the girlies are out of RAM, tragic 🍓
• -ENOSPC — no inode left. none. zero. empty. gone. 🙈

ngl, if you get -EIO because of metadata corruption, that's a whole situation — handle it, don't ignore it bestie 💅

---

🌟 SEE ALSO 🌟

go read these next, iykyk:

• Kernel file ./fs/nilfs2/ifile.c
• struct nilfs_ifile_info(9)
• nilfs_ifile_delete_inode(9)
• nilfs_ifile_count_free_inodes(9)
• nilfs_ifile_read(9)

---

👑 sign-off 👑

and that's the page!! she lives in ./fs/nilfs2, dated October 2026, and she's part of the Kernel API Manual — so next time you're deep in nilfs2 inode allocation, you'll know exactly what's up. periodt. 💜✨🧚

mwah 💋 go create some inodes responsibly