STRUCT GHES_TASK_WORK(9)

💅 struct ghes_task_work(9) — like, the whole page, bestie

okay so this is a page straight out of the Kernel API Manual, and it's all about struct ghes_task_work — a little struct that exists for synchronous RAS event. That's it, that's the whole vibe. Let's get into it ✨

---

🎀 SYNOPSIS 🎀

Here's the actual shape of it, and yes you're gonna want to copy this exactly because structs do not play about spelling:

struct ghes_task_work {
    struct callback_head twork;
    u64 pfn;
    int flags;
 };

Three members. Compact. Iconic. No notes. 🫶

---

🌸 MEMBERS 🌸

• twork — the callback_head for task work. it's the callback head, doing callback head things, for task work. slay.
• pfn — the page frame number of the corrupted page 👀 like, which page is being a problem.
• flags — work control flags 🎀 the knobs that control the work.

---

🦋 DESCRIPTION 🦋

So what even is this struct? It's the structure you use to pass task work along so it gets handled before returning to user-space, and the way that happens is via task_work_add. That's the entire job description. It's giving "little envelope that carries a chore to the kernel's to-do list before we get back to you" energy 💌

ngl this is a short one but that's fine, lowkey every struct deserves its moment 💜

---

🔥 SEE ALSO 🔥

If you wanna go deeper (and you do, bestie), check out the kernel file ./drivers/acpi/apei/ghes.c plus these icon queens:

• ghes_estatus_pool_region_free(9)
• ghes_has_active_errors(9)
• ghes_map_error_status(9)
• ghes_unmap_error_status(9)

---

aaaand that's the page 💖 it lives under ./drivers/acpi/apei, it's dated October 2026, and it's fr fr titled struct ghes_task_work(9). go off, kernel bestie 🌈👑