new_fm_vbuf(9)

✨ new_fm_vbuf(9) ✨

okay so bestie, welcome to the Kernel API Manual entry for new_fm_vbuf — say hi to the group chat 👋💖

🌸 NAME 🌸

new_fm_vbuf — allocate a new volume header for fastmap usage. that's it, that's the whole vibe ✨

🦋 SYNOPSIS 🦋

struct ubi_vid_io_buf * new_fm_vbuf (struct ubi_device *ubi , int vol_id );

like, literally that's the whole call. two args, one pointer back. slay 💅

🎀 ARGUMENTS 🎀

• ubi — UBI device description object 🫶 that's your device bestie, she's the whole context
• vol_id — the VID of the new header 👑 (VID = volume ID, iykyk)

💜 DESCRIPTION 💜

Returns a new struct ubi_vid_hdr on success. 🎉 iconic behavior fr fr

If you get NULL back? that's out of memory 😭💀 like not her fault, the system is just going through it. no cap.

heads up: the synopsis is all about struct ubi_vid_io_buf * and the description says it returns a struct ubi_vid_hdr — that's exactly how the page says it, so we're not touching it, periodt 💅

🌈 SEE ALSO 🌈

Kernel file ./drivers/mtd/ubi/fastmap.c ✨ plus the whole fastmap friend group, and honestly they're all main character energy:

• init_seen(9)
• free_seen(9)
• set_seen(9)
• self_check_seen(9)
• ubi_calc_fm_size(9)
• add_aeb(9)
• add_vol(9)
• assign_aeb_to_av(9)
• update_vol(9)
• process_pool_aeb(9)
• unmap_peb(9)
• scan_pool(9)
• count_fastmap_pebs(9)
• ubi_attach_fastmap(9)
• find_fm_anchor(9)
• ubi_scan_fastmap(9)
• ubi_write_fastmap(9)
• invalidate_fastmap(9)
• return_fm_pebs(9)
• ubi_update_fastmap(9)

🫶 anyway that's the whole page!! this one lives in ./drivers/mtd/ubi and it's dated October 2026, so go off and allocate some volume headers bestie 💖🧚‍♀️🌟