PROBE::KPROCESS.RE(3stap)

💖 NAME 💖

probe::kprocess.release — it's giving process released, bestie 🦋

---

✨ SYNOPSIS ✨

probe kprocess.release {}

---

🎀 VALUES 🎀

okay so when this bad boy fires, you get these little gifts, and we're gonna go through every single one, no skips 💅

• released_pid — the PID of the process that's getting released. like, the actual star of the show 👑
• pid — literally the same thing as released_pid, it's just here for compatibility and it's deprecated, so… ngl, use released_pid instead, fr fr 🙈
• released_tid — the TID of the task being released. yes, task, not process, they're different, iykyk 🧚
• task — a task handle pointing at the process being released. your lil backstage pass to the whole thing 🎟️

---

🌸 CONTEXT 🌸

So the context here? It's the context of the parent — but only if that parent actually wanted to be notified about this process' termination. If it didn't? Then it's just the context of the process itself. vibe check on the parent's boundaries, honestly 🫶

---

💜 DESCRIPTION 💜

This fires when a process is released from the kernel. Periodt. ✨

And the tea is: this always follows a kprocess.exit — it does not come first, it comes after, no cap. BUT (and this is the part you need to hear) it may be delayed somewhat if the process is waiting around in a zombie state 🧟 like, it's just chilling there undead, and the release is lowkey on hold until it's done. so don't be surprised if there's a lil gap, bestie 😭

---

👑 SEE ALSO 👑

• tapset::kprocess(3stap) — go read the whole family, it's iconic 🌈

---

okay that's the whole page, you ate that 💅 this was SystemTap Tapset Reference, September 2026, and yes you read the whole thing so you're officially the main character now 🎀⭐ bye bestie, go trace something 🔥