register_tr...ule_notifier(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… register_tr...ule_notifier(9) β€” like, the Kernel API Manual page, bestie πŸŽ€

okay so picture this: it's a (9) manpage, it lives in the Kernel API Manual, and the title got truncated by the terminal gremlins into register_tr...ule_notifier(9). yes the ellipsis is canon, we respect it 🫢 the full name is right there in NAME, keep reading.


✨ NAME ✨

register_tracepoint_module_notifier β€” registers a tracepoint coming/going notifier πŸ’« like it literally just signs your notifier block up to get pinged whenever a module shows up or dips out.


🌸 SYNOPSIS 🌸

int register_tracepoint_module_notifier (struct notifier_block *nb );

that's the whole vibe. one arg, returns an int. slay.


πŸ¦‹ ARGUMENTS πŸ¦‹

  • nb β€” the notifier block. that's it, that's the argument. your notifier block. the block of notifier. πŸ’…

πŸ’– DESCRIPTION πŸ’–

so the notifiers you register with this function get called on module coming/going β€” like, module arrives, module leaves, notifications go brrr πŸ”₯ β€” and the whole time that happens, it's all happening with the tracepoint_module_list_mutex held. lock held, bestie. do not forget the lock is held.

and the notifier block callback? it should expect a "struct tp_module" data pointer. that's the data it gets handed. no surprises, no cap, just a struct tp_module pointer coming your way πŸŽ€

okay tiny heads-up: since the mutex is held while your callback runs, please don't do anything cursed in there πŸ™ˆ the page doesn't tell me more than that, so I'm not gonna invent drama β€” but like, the lock is held. noted. memorised. manifesting good behaviour.

πŸ”₯ SEE ALSO πŸ”₯


and that's the page!! 🌈 sign-off time: this little icon comes to you from the ./kernel directory, dated October 2026, and it answers to the name register_tr...ule_notifier(9) β€” yes, same truncated name, she's consistent πŸ‘‘ πŸ¦‹ mwah, go read your notifier blocks, ily πŸ’œ

πŸ“¦ where this page comes from