dbg_is_lsave_dirty(9)

✨ dbg_is_lsave_dirty ✨

Okay so, bestie, this is a kernel API manual page, and the manual name is literally dbg_is_lsave_dirty(9). We're diving into UBIFS internals and it's giving ✨filesystem forensics✨. Let's go! 🫶

💖 NAME 💖

dbg_is_lsave_dirty — determine if a lsave node is dirty. That's it. That's the whole vibe check. 💅

🎀 SYNOPSIS 🎀

int dbg_is_lsave_dirty (struct ubifs_info *c , int lnum , int offs );

🌸 ARGUMENTS 🌸

• c — the UBIFS file-system description object. It's the main character struct, honestly. 👑
• lnum — LEB number where lsave node was written. That's the location, bestie. 📍
• offs — offset where lsave node was written. Like, the exact spot within the LEB. 🎯

🦋 SEE ALSO 🦋

No cap, this list is long and it's literally the whole squad of LPT commit functions and debug helpers, all from the kernel file ./fs/ubifs/lpt_commit.c:

• first_dirty_cnode(9)
• next_dirty_cnode(9)
• get_cnodes_to_commit(9)
• upd_ltab(9)
• alloc_lpt_leb(9)
• layout_cnodes(9)
• realloc_lpt_leb(9)
• write_cnodes(9)
• next_pnode_to_dirty(9)
• add_pnode_dirt(9)
• do_make_pnode_dirty(9)
• make_tree_dirty(9)
• need_write_all(9)
• lpt_tgc_start(9)
• lpt_tgc_end(9)
• populate_lsave(9)
• nnode_lookup(9)
• make_nnode_dirty(9)
• make_pnode_dirty(9)
• make_ltab_dirty(9)
• make_lsave_dirty(9)
• make_node_dirty(9)
• get_lpt_node_len(9)
• get_pad_len(9)
• get_lpt_node_type(9)
• is_a_node(9)
• lpt_gc_lnum(9)
• lpt_gc(9)
• ubifs_lpt_start_commit(9)
• free_obsolete_cnodes(9)
• ubifs_lpt_end_commit(9)
• ubifs_lpt_post_commit(9)
• first_nnode(9)
• next_nnode(9)
• ubifs_lpt_free(9)
• dbg_is_all_ff(9)
• dbg_is_nnode_dirty(9)
• dbg_is_pnode_dirty(9)
• dbg_is_ltab_dirty(9)
• dbg_is_node_dirty(9)
• dbg_check_ltab_lnum(9)
• dbg_check_ltab(9)
• dbg_chk_lpt_free_spc(9)
• dbg_chk_lpt_sz(9)
• dump_lpt_leb(9)
• ubifs_dump_lpt_lebs(9)
• dbg_populate_lsave(9)

And that's the whole page, bestie! This one's from the ./fs/ubifs directory, dated October 2026. Slay. 💅✨