ubifs_tnc_remove_range(9)

💅 ubifs_tnc_remove_range (9) — the Kernel API Manual, bestie edition

okay so bestie, welcome to the Kernel API Manual entry for ubifs_tnc_remove_range — and yes, she's a function, and yes, she's iconic. Let's get into it ✨

---

🌸 NAME 🌸

ubifs_tnc_remove_range — remove index entries in range. That's it, that's the whole vibe. She removes them. In a range. Slay 💅

---

🦋 SYNOPSIS 🦋

int ubifs_tnc_remove_range (struct ubifs_info *c , union ubifs_key *from_key , union ubifs_key *to_key );

like, look at her. three args. no notes. 🔥

---

🎀 ARGUMENTS 🎀

• c — the UBIFS file-system description object. yeah, she's the whole filesystem in a trenchcoat, main character energy fr.
• from_key — lowest key to remove. the beginning of the era. the start of the situation. 🫶
• to_key — highest key to remove. where the era ends. closing the group chat, respectfully 💀

---

⭐ DESCRIPTION ⭐

okay so what does she actually do? This function removes index entries starting at from_key and ending at to_key 💖 inclusive of both ends, bestie — the range is the moment.

And what does she give you back? This function returns zero in case of success and a negative error code in case of failure. So like — 0 = we ate, we devoured, no crumbs. negative = something went sideways and she's telling you about it 😭

lowkey important: success is 0, failure is a negative error code. do not mix these up. do not be that person. 🙈

---

🌈 SEE ALSO 🌈

omg the friend group. the whole entire friend group. she does not go anywhere alone, iykyk 👑

The Kernel file ./fs/ubifs/tnc.c and, like, literally everyone she knows:

• insert_old_idx(9)
• insert_old_idx_znode(9)
• ins_clr_old_idx_znode(9)
• destroy_old_idx(9)
• copy_znode(9)
• add_idx_dirt(9)
• replace_znode(9)
• dirty_cow_znode(9)
• lnc_add(9)
• lnc_free(9)
• tnc_read_hashed_node(9)
• try_read_node(9)
• fallible_read_node(9)
• matches_name(9)
• get_znode(9)
• tnc_next(9)
• tnc_prev(9)
• resolve_collision(9)
• fallible_matches_name(9)
• fallible_resolve_collision(9)
• matches_position(9)
• resolve_collision_directly(9)
• dirty_cow_bottom_up(9)
• ubifs_lookup_level0(9)
• lookup_level0_dirty(9)
• maybe_leb_gced(9)
• ubifs_tnc_locate(9)
• ubifs_tnc_get_bu_keys(9)
• read_wbuf(9)
• validate_data_node(9)
• ubifs_tnc_bulk_read(9)
• do_lookup_nm(9)
• ubifs_tnc_lookup_nm(9)
• ubifs_tnc_lookup_dh(9)
• correct_parent_keys(9)
• insert_zbranch(9)
• tnc_insert(9)
• ubifs_tnc_add(9)
• ubifs_tnc_replace(9)
• ubifs_tnc_add_nm(9)
• tnc_delete(9)
• ubifs_tnc_remove(9)
• ubifs_tnc_remove_nm(9)
• ubifs_tnc_remove_dh(9)
• key_in_range(9)
• ubifs_tnc_remove_ino(9)
• ubifs_tnc_next_ent(9)
• tnc_destroy_cnext(9)
• ubifs_tnc_close(9)
• left_znode(9)
• right_znode(9)
• lookup_znode(9)
• is_idx_node_in_tnc(9)
• is_leaf_node_in_tnc(9)
• ubifs_tnc_has_node(9)
• ubifs_dirty_idx_node(9)
• dbg_check_inode_size(9)

every single one. no cap. she's thorough like that 🧚

---

aaand that's the page bestie!! 🍓 this whole moment lives in ./fs/ubifs, dated October 2026, and it's the ubifs_tnc_remove_range(9) page — thanks for reading, ily, go remove some entries in a range 💜💖✨