do_work(9)

🦋 do_work(9) 🦋

okay so welcome to the Kernel API Manual, bestie — today’s main character is do_work(9), and she is here to do one pending work. 💅

🎀 NAME 🎀

do_work — do one pending work.

✨ SYNOPSIS ✨

int do_work (struct ubi_device *ubi , int *executed );

💅 ARGUMENTS 💅

• ubi — the UBI device description object. That’s the device situation you’re working with, bestie. 🫶
• executed — whether there is one work executed. Literally the “did one work execute?” indicator. 👑

🌸 DESCRIPTION 🌸

Okay so here’s the tea: do_work returns zero in case of success and a negative error code in case of failure. No cap. 🔥

If executed is not NULL and there is one work executed, executed is set as 1, otherwise executed is set as 0. That’s the whole vibe check. ✨

🌈 SEE ALSO 🌈

Kernel file ./drivers/mtd/ubi/wl.c — and the whole squad is:

• wl_tree_add(9)
• wl_entry_destroy(9)
• in_wl_tree(9)
• in_pq(9)
• prot_queue_add(9)
• find_wl_entry(9)
• find_mean_wl_entry(9)
• wl_get_wle(9)
• prot_queue_del(9)
• ubi_sync_erase(9)
• serve_prot_queue(9)
• __schedule_ubi_work(9)
• schedule_ubi_work(9)
• schedule_erase(9)
• do_sync_erase(9)
• wear_leveling_worker(9)
• ensure_wear_leveling(9)
• __erase_worker(9)
• ubi_wl_put_peb(9)
• ubi_wl_scrub_peb(9)
• ubi_wl_flush(9)
• ubi_bitflip_check(9)
• tree_destroy(9)
• ubi_thread(9)
• shutdown_work(9)
• erase_aeb(9)
• ubi_wl_init(9)
• protection_queue_destroy(9)
• ubi_wl_close(9)
• self_check_ec(9)
• self_check_in_wl_tree(9)
• self_check_in_pq(9)
• produce_free_peb(9)
• ubi_wl_get_peb(9)

and that’s the page, bestie 🫶 source/version: ./drivers/mtd/ubi · date: October 2026 · page: do_work(9) 💖