ubifs_add_lpt_dirt(9)

💅 ubifs_add_lpt_dirt(9) 💅

okay bestie, this little icon is straight out of the Kernel API Manual, and it's here to explain one very specific LPT chore. no cap, it's giving “tiny function, big filesystem energy.” 🦋

✨ NAME ✨

ubifs_add_lpt_dirt — add dirty space to LPT LEB properties. literally that's the whole job, and it ate. 💅

🌸 SYNOPSIS 🌸

void ubifs_add_lpt_dirt (struct ubifs_info *c , int lnum , int dirty );

🎀 ARGUMENTS 🎀

• c — the UBIFS file-system description object. your main character struct, iykyk. 👑
• lnum — the LEB number to which to add dirty space. yes, that exact LEB. 🎯
• dirty — the amount of dirty space to add. the dirty little number itself. 😭

💖 SEE ALSO 💖

go peek at the kernel file ./fs/ubifs/lpt.c, and then lowkey go bother these iconic cross-refs: do_calc_lpt_geom(9), ubifs_calc_lpt_geom(9), calc_dflt_lpt_geom(9), pack_bits(9), ubifs_unpack_bits(9), ubifs_pack_pnode(9), ubifs_pack_nnode(9), ubifs_pack_ltab(9), ubifs_pack_lsave(9), set_ltab(9), ubifs_add_nnode_dirt(9), add_pnode_dirt(9), calc_nnode_num(9), calc_nnode_num_from_parent(9), calc_pnode_num_from_parent(9), ubifs_create_dflt_lpt(9), update_cats(9), replace_cats(9), check_lpt_crc(9), check_lpt_type(9), unpack_pnode(9), ubifs_unpack_nnode(9), unpack_ltab(9), unpack_lsave(9), validate_nnode(9), validate_pnode(9), set_pnode_lnum(9), ubifs_read_nnode(9), read_pnode(9), read_ltab(9), read_lsave(9), ubifs_get_nnode(9), ubifs_get_pnode(9), ubifs_pnode_lookup(9), ubifs_lpt_lookup(9), dirty_cow_nnode(9), dirty_cow_pnode(9), ubifs_lpt_lookup_dirty(9), ubifs_lpt_calc_hash(9), lpt_check_hash(9), lpt_init_rd(9), lpt_init_wr(9), ubifs_lpt_init(9), struct lpt_scan_node(9), scan_get_nnode(9), scan_get_pnode(9), ubifs_lpt_scan_nolock(9), dbg_chk_pnode(9), dbg_check_lpt_nodes(9). slay, that's the whole squad. 🌈

sign-off bestie: this page came from ./fs/ubifs, dated October 2026 💋🎀✨