nilfs_bmap_insert(9)

💖 nilfs_bmap_insert(9) 💖

okay so bestie, welcome to the Kernel API Manual page for nilfs_bmap_insert — yes that's the whole name, yes it's a mouthful, we love her anyway 🫶

---

✨ NAME ✨

nilfs_bmap_insert — insert a new key-record pair into a bmap 👑

🌸 SYNOPSIS 🌸

int nilfs_bmap_insert (struct nilfs_bmap *bmap , __u64 key , unsigned
long rec );

literally the whole signature, no cap 🎀

🦋 ARGUMENTS 🦋

• bmap — the bmap. that's it. that's the description. she's a bmap. iconic minimalism 💅
• key — the key. again, extremely self-explanatory, the kernel devs were in their brevity era 😭
• rec — the record. yep. we're just naming the parameters at this point, and honestly? respect 🙈

💜 DESCRIPTION 💜

so the way that nilfs_bmap_insert works is: it takes the brand-new key-record pair you specified with key and rec, and it inserts that pair into bmap. that's the whole vibe. new pair, go into the bmap, slay ✨

🌈 RETURN 🌈

on success you get 0 — periodt, we love a clean zero 💖

but on failure you get one of these negative error codes, and no bestie, none of them are a good time:

• -EEXIST — a record associated with key already exists 😭 so like… it's already there. she's taken.
• -EIO — I/O error, and yes, that includes metadata corruption 💀 not the cute kind of drama.
• -ENOMEM — insufficient memory available. the memory said "no <3" 🍓

🔥 SEE ALSO 🔥

kernel file ./fs/nilfs2/bmap.c — that's where she lives 🧚

and the whole friend group, all in one glow-up list:

• nilfs_bmap_lookup_at_level(9)
• nilfs_bmap_seek_key(9)
• nilfs_bmap_delete(9)
• nilfs_bmap_truncate(9)
• nilfs_bmap_clear(9)
• nilfs_bmap_propagate(9)
• nilfs_bmap_lookup_dirty_buffers(9)
• nilfs_bmap_assign(9)
• nilfs_bmap_mark(9)
• nilfs_bmap_test_and_clear_dirty(9)
• nilfs_bmap_read(9)
• nilfs_bmap_write(9)

---

and that's the page, bestie!! brought to you by ./fs/nilfs2, dated October 2026, from the nilfs_bmap_insert(9) crew — go forth and insert responsibly 🌸💅