atomic_notifier_call_chain(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… atomic_notifier_call_chain(9) β€” Kernel API Manual ✨

okay so bestie, welcome to the Kernel API Manual, section 9 β€” this page is literally about calling functions in an atomic notifier chain, and it ate. 🫢


🌸 NAME 🌸

atomic_notifier_call_chain β€” Call functions in an atomic notifier chain πŸ’–

✨ SYNOPSIS ✨

       int atomic_notifier_call_chain (struct atomic_notifier_head *nh ,
       unsigned long val , void *v );

πŸŽ€ ARGUMENTS πŸŽ€

  • nh β€” Pointer to head of the atomic notifier chain. That’s the main character of this call, bestie. πŸ‘‘
  • val β€” Value passed unmodified to notifier function. Like, no edits, no filters β€” it goes through as-is. ✨
  • v β€” Pointer passed unmodified to notifier function. Same vibe: untouched, unbothered. πŸ¦‹

πŸ’« DESCRIPTION πŸ’«

Calls each function in a notifier chain in turn. The functions run in an atomic context, so they must not block. 🚨 This routine uses RCU to synchronize with changes to the chain.

If the return value of the notifier can be and'ed with NOTIFY_STOP_MASK then atomic_notifier_call_chain will return immediately, with the return value of the notifier function which halted execution. Otherwise the return value is the return value of the last notifier function called. πŸ’…

okay but fr fr: β€œatomic context” means no blocking, bestie β€” that part is not a drill. 😭

πŸ‘€ SEE ALSO πŸ‘€


Later, bestie 🫢 β€” source/version: ./kernel, date: October 2026, page: atomic_notifier_call_chain(9). Mwah πŸ’‹

πŸ“¦ where this page comes from