update_ftrace_direct_del(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… update_ftrace_direct_del(9) β€” the Kernel API Manual tea β˜•βœ¨

okay bestie, buckle up, we're in the Kernel API Manual today and this one is genuinely a little baddie πŸŽ€


✨ NAME ✨

update_ftrace_direct_del β€” updates @ops by removing its direct callers provided in @hash 🧚


🌸 SYNOPSIS 🌸

int update_ftrace_direct_del (struct ftrace_ops *ops , struct ftrace_hash *hash );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • ops β€” the address of the struct ftrace_ops object πŸ’–
  • hash β€” the address of the struct ftrace_hash object 🌈

πŸ”₯ DESCRIPTION πŸ”₯

so what this one does is delete custom direct callers (that's ip -> addr, iykyk) over in ops, and it takes them from the ones you specified via hash. that's the whole vibe. πŸ’…

after it does its thing, the ops will be either unregistered updated. yes that's exactly what the manual says, no I'm not gonna editorialize, that's the sentence, we're moving on 🫢


⭐ RETURN ⭐

  • zero on success β€” that's the slay ✨
  • Non zero on error 😭 β€” which includes:
    • -EINVAL β€” the hash is empty
    • -EINVAL β€” the ops is not registered
not me getting the same -EINVAL for two completely different problems πŸ’€ check both, bestie.

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./kernel/trace/ftrace.c and literally the entire friend group:


bestie this page is brought to you by the source/version ./kernel/trace, dated October 2026 πŸ—“οΈπŸ’œ go read it in ftrace.c, it ate, no cap πŸ“

update_ftrace_direct_del(9) πŸŽ€ periodt ✨

πŸ“¦ where this page comes from