next_peb_for_wl(9)

🎀 NAME 🎀

okay so bestie, welcome to the next_peb_for_wl(9) page in the Kernel API Manual 💖 this one is short and sweet: it returns next PEB to be used internally by the WL subsystem. that's the whole name, no cap.

✨ SYNOPSIS ✨

here's the exact signature, character for character, because we do not play with code:

struct ubi_wl_entry * next_peb_for_wl (struct ubi_device *ubi , bool need_fill );

yep, it returns a struct ubi_wl_entry *, and it takes a struct ubi_device * plus a bool. iconic.

💅 ARGUMENTS 💅

• ubi — UBI device description object. that's the object you hand over, bestie 🫶
• need_fill — whether to fill wear-leveling pool when no PEBs are found. literally what the bool is for, no guessing ✨

🔥 SEE ALSO 🔥

the page points at the kernel file ./drivers/mtd/ubi/fastmap-wl.c, and the whole SEE ALSO squad is here — every single one, periodt:

• Kernel file ./drivers/mtd/ubi/fastmap-wl.c — the kernel file listed on the page 🦋
• update_fastmap_work_fn(9)
• find_anchor_wl_entry(9)
• return_unused_pool_pebs(9)
• ubi_wl_get_fm_peb(9)
• ubi_refill_pools_and_lock(9)
• produce_free_peb(9)
• ubi_wl_get_peb(9)
• need_wear_leveling(9)
• ubi_ensure_anchor_pebs(9)
• ubi_wl_put_fm_peb(9)
• ubi_is_erase_work(9)
• may_reserve_for_fm(9)

okay bye bestie — this page is from source/version ./drivers/mtd/ubi, dated October 2026, and it's the next_peb_for_wl(9) manual. mwah 💋💖