fill_gap(9)

💖 NAME 💖

okay bestie, welcome to the fill_gap(9) page from the Kernel API Manual 💖 This is the function that will make index nodes in gaps in dirty index LEBs. That’s the whole name vibe, and honestly? iconic 🎀

✨ SYNOPSIS ✨

int fill_gap (struct ubifs_info *c , int lnum , int gap_start , int gap_end , int *dirt );

🎀 ARGUMENTS 🎀

• c — the UBIFS file-system description object, aka the main character of this little operation 🦋
• lnum — the LEB number that the gap appears in, no cap 📌
• gap_start — offset of start of gap, right at the beginning of the gap energy ✨
• gap_end — offset of end of gap, where the gap finishes its little era 💅
• dirt — adds dirty space to this, periodt 🫶

💅 DESCRIPTION 💅

This function returns the number of index nodes written into the gap. That’s the description, bestie — short, sweet, and very much to the point 🌸

🌈 SEE ALSO 🌈

Kernel file ./fs/ubifs/tnc_commit.c — yes, that’s the spot 👑

The whole SEE ALSO crew, gathered for the group chat:

• make_idx_node(9)
• find_old_idx(9)
• is_idx_node_in_use(9)
• layout_leb_in_gaps(9)
• get_leb_cnt(9)
• layout_in_gaps(9)
• layout_in_empty_space(9)
• layout_commit(9)
• find_first_dirty(9)
• find_next_dirty(9)
• get_znodes_to_commit(9)
• alloc_idx_lebs(9)
• free_unused_idx_lebs(9)
• free_idx_lebs(9)
• ubifs_tnc_start_commit(9)
• write_index(9)
• free_obsolete_znodes(9)
• return_gap_lebs(9)
• ubifs_tnc_end_commit(9)

mwah 💋 — signed off from ./fs/ubifs, October 2026, all about fill_gap(9) 🫶