do_notify_parent_cldstop(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ do_notify_parent_cldstop(9) ✨

okay so bestie, we're in the Kernel API Manual today and the function we're stanning is do_notify_parent_cldstop β€” say it with me, it's a whole mouthful but it's iconic. πŸŽ€


πŸ’– NAME πŸ’–

do_notify_parent_cldstop β€” notify parent of stopped/continued state change

like literally the whole job is "hey parent, something changed" and honestly? relatable. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

void do_notify_parent_cldstop (struct task_struct *tsk , bool
for_ptracer , int why );

no cap, that's the whole signature. three args, zero drama. ✨


🌸 ARGUMENTS 🌸

  • tsk β€” the task that's out here reporting the state change. main character energy fr fr. πŸ‘‘
  • for_ptracer β€” this one's a yes/no baddie: the notification is for the ptracer. that's it, that's the whole flag. 🫢
  • why β€” the reason, and it's one of CLD_{CONTINUED|STOPPED|TRAPPED} to report. pick one, bestie, it's giving multiple choice. 🌈

πŸ’€ DESCRIPTION πŸ’€

Notifies tsk's parent that the stopped/continued state has changed. like a little "hey mom, status update" text but for processes. 😭

So here's the tea: if for_ptracer is false, then tsk's group leader notifies to its real parent. If it's true, then tsk reports to tsk->parent, which should be the ptracer. two different pathways, both valid, both slay. ✨


πŸ”₯ CONTEXT πŸ”₯

⚠️ Must be called with tasklist_lock at least read locked.

not me reminding you twice β€” but like, genuinely, do not skip this. it's a lock requirement, not a suggestion, bestie. πŸ™ˆ


🧚 SEE ALSO 🧚

Kernel file ./kernel/signal.c and the whole friend group:

that's 26 entries, i counted, and yes i listed every single one because we don't do "etc." in this house. πŸ’œ


okay that's the whole page!! πŸ“ this little cutie lives in ./kernel and the version stamp is October 2026 β€” remember when that felt like the future?? anyway, mwah, go read signal.c, ily, bye!! πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from