ubi_eba_is_mapped(9)

ubi_eba_is_mapped(9) 💅

okay so welcome to the Kernel API Manual page for ubi_eba_is_mapped(9) — yes, the manual name is literally right there, we’re folded and situated, bestie. This one is a tiny little bool-check with main character energy, no cap.

🌸 NAME 🌸

ubi_eba_is_mapped — check if a LEB is mapped. That’s the whole name, and it ate. 💖

✨ SYNOPSIS ✨

bool ubi_eba_is_mapped (struct ubi_volume *vol , int lnum );

That signature is iconic and also exactly what you need to call it. Periodt.

🎀 ARGUMENTS 🎀

• vol — volume description object. Your volume bestie. 🫶
• lnum — logical eraseblock number. The number of the LEB you’re checking, iykyk. 🔥

🦋 DESCRIPTION 🦋

This function returns true if the LEB is mapped, and false otherwise. That’s it. That’s the whole plot. 💀✨ No hidden side quest, no extra lore in this page.

🌈 SEE ALSO 🌈

okay bestie, here’s the whole reference squad, all present and accounted for:

• Kernel file ./drivers/mtd/ubi/eba.c
• struct ubi_eba_entry(9)
• struct ubi_eba_table(9)
• ubi_next_sqnum(9)
• ubi_get_compat(9)
• ubi_eba_get_ldesc(9)
• ubi_eba_create_table(9)
• ubi_eba_destroy_table(9)
• ubi_eba_copy_table(9)
• ubi_eba_replace_table(9)
• ltree_lookup(9)
• ltree_add_entry(9)
• leb_read_lock(9)
• leb_read_unlock(9)
• leb_write_lock(9)
• leb_write_trylock(9)
• leb_write_unlock(9)
• ubi_eba_unmap_leb(9)
• check_mapping(9)
• ubi_eba_read_leb(9)
• ubi_eba_read_leb_sg(9)
• try_recover_peb(9)
• recover_peb(9)
• try_write_vid_and_data(9)
• ubi_eba_write_leb(9)
• ubi_eba_write_leb_st(9)
• is_error_sane(9)
• ubi_eba_copy_leb(9)
• print_rsvd_warning(9)
• self_check_eba(9)
• ubi_eba_init(9)

okay bye bestie 💖 this page came from the source path ./drivers/mtd/ubi, dated October 2026, and it’s the ubi_eba_is_mapped(9) page from the Kernel API Manual. mwah 🫶✨