unregister_trigger(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… unregister_trigger(9) β€” like, the *un*register one, bestie

okay so welcome to unregister_trigger(9), part of the Kernel API Manual lineup πŸŽ€ (yes that's the manual name, we're fancy here). This is the page where we learn how to take things back out of the event trigger system. Un-register. Un-do. The breakup era of trigger land πŸ’”βœ¨


🌸 SYNOPSIS 🌸

void unregister_trigger (char *glob , struct event_trigger_data *test ,
struct trace_event_file *file );

like, three arguments, returns nothing (void), very low-maintenance of it honestly 🫢


✨ ARGUMENTS ✨

  • glob β€” the raw string you used to register the trigger in the first place. the original receipt, bestie 🧾
  • test β€” trigger-specific data used to find the trigger to remove. think of it as the vibe-check you run to confirm this is the one we're dropping πŸ™ˆ
  • file β€” the trace_event_file associated with the event. the event's home address, basically 🏠

πŸ’œ DESCRIPTION πŸ’œ

Common implementation for event trigger unregistration. that's it, that's the job 🫑

Usually used directly as the unreg method in event command implementations. so it's not even a "call this yourself" situation β€” it's the standard-issue, plug-it-in piece that event commands reach for. iconic outsourcing, no cap πŸ‘‘

fr fr the whole point is: this is the generic unregistration path. if you're writing an event command, you probably just use it as your unreg and move on with your life πŸ¦‹

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./kernel/trace/trace_events_trigger.c β€” go read the source, it's giving main character energy πŸ”₯

like, the whole friend group, honestly πŸ˜­πŸ’–


and that's a wrap bestie!! this page lives in ./kernel/trace and it's stamped October 2026 β€” mwah, slay, periodt πŸ’…πŸŒˆπŸ‘‘

πŸ“¦ where this page comes from