process_pool_aeb(9)

📦 version 7.3.1, in nixpkgs unstable

💅 process_pool_aeb — like, we found a non-empty PEB in a pool 👑

okay so real talk, this page is process_pool_aeb(9) straight out of the Kernel API Manual bestie, and it's way less scary than it sounds, promise 🫶

✨ NAME ✨

process_pool_aeb — we found a non-empty PEB in a pool. that's it, that's the whole vibe 💅 (a PEB = physical erase block, iykyk)

🌸 SYNOPSIS 🌸

int process_pool_aeb (struct ubi_device *ubi , struct ubi_attach_info
*ai , struct ubi_vid_hdr *new_vh , struct ubi_ainf_peb *new_aeb );

literally returns an int, no cap 🔥

🎀 ARGUMENTS 🎀

  • ubi — the UBI device object 🦋 like, the whole device we're working with
  • ai — the attach info object ✨ the lil bundle of info from when we attached
  • new_vh — the volume header derived from new_aeb 👑 it's giving "header that came from the AEB below"
  • new_aeb — the AEB to be examined 🔍 main character of the function tbh, we're inspecting this one

💖 DESCRIPTION 💖

so what happens? it returns 0 on success 🌈 and < 0 means an internal error happened 😭 (yes, strictly less than zero, not "some number," okay bestie, the manpage said < 0).

that's it. that's the description. she's short and iconic 💅

ngl this is one of those tiny helper functions in the fastmap code — if you're reading this page you're probably deep in fastmap.c and that's honestly so brave of you 🫶

🧚 SEE ALSO 🧚

like the whole squad, fr fr. file: ./drivers/mtd/ubi/fastmap.c 💜

like, read them all, they're all so valid ⭐

and that's the whole page bestie 💖 this one came out of ./drivers/mtd/ubi, dated October 2026, and it's filed under process_pool_aeb(9) — go forth and slay your fastmap debugging 🦋✨🎀

📦 where this page comes from