read_add_inode(9)

💖 read_add_inode(9) 💖

okay so we're in the Kernel API Manual, bestie, and this page is literally read_add_inode(9). it's giving kernel helper energy and we're gonna get through it together 🫶

✨ NAME ✨

read_add_inode — reads an inode node and adds it to the RB-tree of inodes. periodt. 💅

🌸 SYNOPSIS 🌸

struct fsck_inode * read_add_inode (struct ubifs_info *c , struct fsck_data *fsckd , ino_t inum );

💅 ARGUMENTS 💅

• c — UBIFS file-system description object. the main-character struct for this whole situation, iykyk.
• fsckd — FS checking information. the fsck data vibe check.
• inum — inode number to read. the exact inode we're pulling up, no cap.

🦋 DESCRIPTION 🦋

okay so here's the tea: this is a helper function for check_leaf. it finds inode node inum in the index, reads it, and adds it to the RB-tree of inodes. slay. ✨

if it works, it returns an inode information pointer. if it doesn't, it returns a negative error code. no cap — failure is literally giving negative error code energy 😭.

🔥 SEE ALSO 🔥

• Kernel file ./fs/ubifs/debug.c
• ubifs_dump_index(9)
• dbg_save_space_info(9)
• dbg_check_space_info(9)
• dbg_check_synced_i_size(9)
• dbg_check_key_order(9)
• dbg_check_znode(9)
• dbg_check_tnc(9)
• dbg_walk_index(9)
• add_size(9)
• dbg_check_idx_size(9)
• struct fsck_inode(9)
• struct fsck_data(9)
• add_inode(9)
• search_inode(9)
• check_leaf(9)
• free_inodes(9)
• check_inodes(9)
• dbg_check_filesystem(9)
• dbg_check_data_nodes_order(9)
• dbg_check_nondata_nodes_order(9)
• provide_user_output(9)
• interpret_user_input(9)
• dbg_debugfs_init_fs(9)
• dbg_debugfs_exit_fs(9)
• dbg_debugfs_init(9)
• dbg_debugfs_exit(9)
• ubifs_debugging_init(9)
• ubifs_debugging_exit(9)

signed off from the ./fs/ubifs source/version, dated October 2026, for read_add_inode(9) 💖 bye bestie 🫶