scan_for_dirty_cb(9)

okay so bestie, welcome to the group chat for scan_for_dirty_cb(9) from the Kernel API Manual — it’s literally the dirty space scan callback, and it’s giving “callback that hands back scan instructions” energy. 🫶✨

✨ NAME ✨

scan_for_dirty_cb — dirty space scan callback. That’s the name, no cap. 💅

🦋 SYNOPSIS 🦋

Here’s the signature, bestie — keep it exact, character for character:

int scan_for_dirty_cb (struct ubifs_info *c , const struct ubifs_lprops
       *lprops , int in_tree , void *arg );

🌸 ARGUMENTS 🌸

These are the four cuties this callback takes in:

• c — the UBIFS file-system description object. 💖
• lprops — the LEB properties to scan. ✨
• in_tree — whether the LEB properties are in main memory. 🎀
• arg — information passed to and from the caller of the scan. 🦋

🔥 DESCRIPTION 🔥

This function returns a code, and that code says whether the scan should keep going (LPT_SCAN_CONTINUE), whether those LEB properties should get added to the tree in main memory (LPT_SCAN_ADD), or whether the scan should stop (LPT_SCAN_STOP). Three outcomes, zero mystery, periodt. 💅

🌈 SEE ALSO 🌈

The Kernel file ./fs/ubifs/find.c is in the chat, plus all these (9) besties:

• struct scan_data(9)
• valuable(9)
• scan_for_dirty(9)
• ubifs_find_dirty_leb(9)
• scan_for_free_cb(9)
• do_find_free_space(9)
• ubifs_find_free_space(9)
• scan_for_idx_cb(9)
• scan_for_leb_for_idx(9)
• ubifs_find_free_leb_for_idx(9)
• ubifs_save_dirty_idx_lnums(9)
• scan_dirty_idx_cb(9)
• find_dirty_idx_leb(9)
• get_idx_gc_leb(9)
• find_dirtiest_idx_leb(9)
• ubifs_find_dirty_idx_leb(9)

🧚✨ cute little sign-off: this page comes from ./fs/ubifs, dated October 2026, and it’s all for scan_for_dirty_cb(9). mwah 💋