ubifs_tnc_bulk_read(9)

💅 ubifs_tnc_bulk_read(9) — the Kernel API Manual page, but make it make sense 🫶

okay bestie, welcome to the Kernel API Manual entry for ubifs_tnc_bulk_read(9). yes the manual name is Kernel API Manual, and yes we're mentioning it up top like the polite little page we are ✨

---

🌸 NAME 🌸

ubifs_tnc_bulk_read — read a number of data nodes in one go.

like, all at once. no cap, no one-at-a-time nonsense. it's giving efficiency 💅

---

🦋 SYNOPSIS 🦋

int ubifs_tnc_bulk_read (struct ubifs_info *c , struct bu_info *bu );

literally the whole signature. look at it. beautiful. int in the front, two struct pointers in the back, iconic 👑

---

🎀 ARGUMENTS 🎀

• c — the UBIFS file-system description object. she's the context, she's the moment, she's everything the function needs to know about the filesystem 💖
• bu — bulk-read parameters and results. so it goes in holding params and comes out holding results, a true dual-threat king 🔥

---

⭐ DESCRIPTION ⭐

so what does this function do? bestie, it reads and validates the data nodes that were identified by the -EAGAIN to indicate a race with GC, or another negative error code on failure. 🧚

and before anyone comes for my girl — yes, that sentence reads a little chopped in the source, it's giving "the intern was sleepy", but I'm not about to invent words that aren't there. the facts stay, the vibe is mine. 💀

lowkey important: -EAGAIN is the "a race with GC happened, try again bestie" signal, and any other negative error code means it just failed. don't ignore the return value, she's talking to you 😭

---

🌈 SEE ALSO 🌈

the whole friend group, and also the kernel file ./fs/ubifs/tnc.c — that's home base, that's where the lore lives 🏠

• 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)
• 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_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)

no skips, no "and others", all of them. we don't do vague here 🫶

---

and that's the page!! 💜 this little number lives in ./fs/ubifs, and the source/version line stamps it October 2026. mwah, kiss the manpage, go read your data nodes in bulk bestie 🎀✨