torture_peb(9)

💅 torture_peb(9) — Kernel API Manual ✨

Okay bestie, welcome to the torture_peb page. This is the Kernel API Manual, and we’re about to vibe-check a physical eraseblock that is supposedly bad. No cap. 🫶

---

🌸 NAME 🌸

torture_peb — test a supposedly bad physical eraseblock.

---

✨ SYNOPSIS ✨

int torture_peb (struct ubi_device *ubi , int pnum );

---

🎀 ARGUMENTS 🎀

• ubi — UBI device description object. It’s giving “the whole device situation.” 💖
• pnum — the physical eraseblock number to test. Literally the PEB number we’re putting under the microscope. 🔍

---

💅 DESCRIPTION 💅

So here’s the tea: this function returns -EIO if the physical eraseblock did not pass the test. 😭

If the test was successfully passed, it returns a positive number of erase operations done. Slay. ✨

And in case of other errors, it returns other negative error codes. Periodt. 💀

---

🦋 SEE ALSO 🦋

Kernel file ./drivers/mtd/ubi/io.c and all these iconic little functions:

• ubi_io_read(9)
• ubi_io_write(9)
• do_sync_erase(9)
• nor_erase_prepare(9)
• ubi_io_sync_erase(9)
• ubi_io_is_bad(9)
• ubi_io_mark_bad(9)
• validate_ec_hdr(9)
• ubi_io_read_ec_hdr(9)
• ubi_io_write_ec_hdr(9)
• validate_vid_hdr(9)
• ubi_io_read_vid_hdr(9)
• ubi_io_write_vid_hdr(9)
• self_check_not_bad(9)
• self_check_ec_hdr(9)
• self_check_peb_ec_hdr(9)
• self_check_vid_hdr(9)
• self_check_peb_vid_hdr(9)
• self_check_write(9)
• ubi_self_check_all_ff(9)

---

Cute lil sign-off: this page’s source/version is ./drivers/mtd/ubi, and the date on it is October 2026. 💖🎀✨