devlink_trap_report(9)
π devlink_trap_report(9) π
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 beNULL, so don't panic if it is π
π§ SEE ALSO π§
the whole friend group, no cap:
- Kernel file
./net/devlink/trap.c struct devlink_trap_policer_item(9)struct devlink_trap_group_item(9)struct devlink_trap_item(9)devl_traps_register(9)devlink_traps_register(9)devl_traps_unregister(9)devlink_traps_unregister(9)devlink_trap_ctx_priv(9)devl_trap_groups_register(9)devlink_trap_groups_register(9)devl_trap_groups_unregister(9)devlink_trap_groups_unregister(9)devl_trap_policers_register(9)devl_trap_policers_unregister(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms