rethook_stop(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

Okay so welcome to the rethook_stop(9) page, a certified Kernel API Manual banger πŸŽ€ β€” and the whole vibe here is: rethook_stop β€” stop using a rethook. That's it, that's the tweet. Short, sweet, iconic πŸ‘‘


✨ SYNOPSIS ✨

void rethook_stop (struct rethook *rh );

Yes bestie, that's the entire signature, no cap. It returns void, don't @ me πŸ’…


🫢 ARGUMENTS 🫢

  • rh β€” the struct rethook you want to stop. That's the one. Hand it over 🫴

🌸 DESCRIPTION 🌸

So here's the tea β˜• β€” you call rethook_stop to stop using a rethook, and the whole reason you do that is to prepare for freeing it 🧚✨ Like, you're packing up the rethook's little room before it gets demolished, that's the energy.

Now this is the part where you need to pay attention, because it's giving "read the instructions or perish" 😭 If you want to wait for all running rethook handler before you call rethook_free, then you genuinely need to call this first, and wait RCU, and then call rethook_free. In that order. Periodt πŸ”₯

Not me stressing that skipping the RCU wait is a whole situation β€” the sequence is literally: rethook_stop, wait RCU, rethook_free. Don't shuffle it πŸ™ˆ

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./kernel/trace/rethook.c plus the whole friend group πŸ’œ:


And that's the page, bestie 🌈 β€” brought to you by ./kernel/trace, dated October 2026, page rethook_stop(9). Slay, go stop some rethooks responsibly πŸ’…βœ¨πŸ“

πŸ“¦ where this page comes from