devlink_trap_report(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the devlink_trap_report(9) page β€” it lives in the Kernel API Manual and it's literally the function that tells drop monitor "hey, we caught a trapped packet πŸŽ€". It's short, it's sweet, it's giving tiny-iconic-manpage energy.


✨ NAME ✨

devlink_trap_report β€” report a trapped packet to drop monitor. that's it, that's the whole gig 🫢


🌸 SYNOPSIS 🌸

void devlink_trap_report (struct devlink *devlink , struct sk_buff *skb
, void *trap_ctx , struct devlink_port *in_devlink_port , const struct
flow_action_cookie *fa_cookie );
it returns void, so there's no return value to obsess over. it just does the thing and dips πŸ’…

πŸ¦‹ ARGUMENTS πŸ¦‹

five args, all of them matter, let's go one by one:

  • devlink β€” the devlink. yes bestie, that's the whole description. it's the devlink instance you're working with, main character energy πŸ‘‘
  • skb β€” the trapped packet itself πŸ“
  • trap_ctx β€” the trap context ✨
  • in_devlink_port β€” the input devlink port, like the port the packet came in through 🌈
  • fa_cookie β€” the flow action cookie. and listen β€” this one could be NULL, so don't panic if it is πŸ™ˆ

🧚 SEE ALSO 🧚

the whole friend group, no cap:

like, go read those too, iykyk πŸ’€


and that's the page!! mwah πŸ’‹ this lil doc came from the source path ./net/devlink, dated October 2026, and yes it's filed under devlink_trap_report(9) β€” catch you in the next manpage bestie, slay πŸŽ€βœ¨

πŸ“¦ where this page comes from