ubi_sync_erase(9)

✨ NAME ✨

okay so this is ubi_sync_erase(9) from the Kernel API Manual, and it's giving exactly one job: synchronously erase a physical eraseblock. periodt. 💅

🦋 SYNOPSIS 🦋

int ubi_sync_erase (struct ubi_device *ubi , struct ubi_wl_entry *e ,
       int *torture );

🎀 ARGUMENTS 🎀

• ubi — UBI device description object. iconic little descriptor.
• e — the physical eraseblock to erase.
• torture — if the physical eraseblock has to be tortured; cleared to zero once the torture test has completed successfully so that a retry of the erase does not torture the physical eraseblock again. iykyk 🫶

🌈 DESCRIPTION 🌈

This function returns zero in case of success and a negative error code in case of failure. No cap: zero = success, negative error code = failure, and that's the whole vibe check. ✨

🔥 SEE ALSO 🔥

Kernel file ./drivers/mtd/ubi/wl.c is the source bestie, and these refs are all invited to the group chat:

• wl_tree_add(9)
• wl_entry_destroy(9)
• do_work(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)
• 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)

okay bye bestie 💖 source/version: ./drivers/mtd/ubi; date: October 2026 — ubi_sync_erase(9) out. slay. 💅