zpci_clear_error_state(9)

💅 zpci_clear_error_state — the Kernel API Manual said what it said

Okay bestie, so this one is zpci_clear_error_state from the Kernel API Manual, and honestly? It does exactly one thing and it does it with main character energy: it wipes the zPCI error state off a device. Clean slate, fresh start, aura restored. ✨

---

🎀 SYNOPSIS 🎀

int zpci_clear_error_state (struct zpci_dev *zdev );

Yep. That's the whole signature. One argument, returns an int. Iconic, lowkey.

---

🌸 ARGUMENTS 🌸

• zdev — the zdev whose zPCI error state you want reset. Like, that's your girl right there. She's the one getting un-errored. 🫶

---

✨ DESCRIPTION ✨

So here's the vibe: you call this, and it clears the zPCI error state of the device. Bada bing, bada boom. 💫

But listen — and this is the important part, so don't skip it — if clearing the zPCI error state fails, the device is just... left in the error state. No rescue, no glow-up. It stays in its flop era. 😭

And in that case, it may make sense to call zpci_io_perm_failure on the associated pdev, but only if it exists. That's the "may make sense" — not a promise, just a suggestion, iykyk. 🙈

Not me writing this with zero % guarantee: fail = device stays errored, and that's just how it is. Plan accordingly, bestie. 💀

---

⭐ RETURN ⭐

• 0 on success — slay, we ate 🍓
• -EIO otherwise — it's giving "the I/O said no" 💔

---

🌈 SEE ALSO 🌈

Look at this friend group, literally all of them:

• Kernel file ./arch/s390/pci/pci.c
• zpci_hot_reset_device(9)
• zpci_create_device(9)
• zpci_add_device(9)
• zpci_scan_configured_device(9)
• zpci_deconfigure_device(9)
• zpci_device_reserved(9)
• zpci_reset_load_store_blocked(9)

---

k bye bestie 💖 — this page came to you from ./arch/s390/pci, dated October 2026, and yes it's still zpci_clear_error_state(9) because we don't do rebranding around here. 👑