batadv_bla_tx(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– batadv_bla_tx(9) πŸ’–

okay so bestie, welcome to the batadv_bla_tx(9) page from the Kernel API Manual β€” this one is all about checking packets going into the mesh, and it is genuinely giving kernel networking main character energy ✨

🌸 NAME 🌸

batadv_bla_tx β€” check packets going into the mesh

πŸ¦‹ SYNOPSIS πŸ¦‹

       bool batadv_bla_tx (struct batadv_priv *bat_priv , struct sk_buff *skb ,
       unsigned short vid );

πŸŽ€ ARGUMENTS πŸŽ€

  • bat_priv β€” the bat priv with all the mesh interface information. Like, it has all the mesh interface info HQ vibes πŸ’…
  • skb β€” the frame to be checked. This is the packet bestie we are vibe-checking.
  • vid β€” the VLAN ID of the frame. Important little detail, periodt.

πŸ”₯ DESCRIPTION πŸ”₯

batadv_bla_tx checks if:

  • a claim was received which has to be processed
  • the frame is allowed on the mesh

in these cases, the skb is further handled by this function.

⚠️ Warning: This function may reallocate the skb data buffer via batadv_bla_process_claim/... Any pointer into the skb data (e.g. obtained from skb->data or eth_hdr) before this call must be considered invalid afterwards and has to be reacquired. Like fr fr, do not hold onto that pointer β€” it is giving stale the second this function does its thing 😭

⭐ RETURN ⭐

true if handled, otherwise it returns false and the caller shall further process the skb.

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./net/batman-adv/bridge_loop_avoidance.c


xoxo, from ./net/batman-adv β€” October 2026 edition, page batadv_bla_tx(9) πŸ«ΆπŸ’–

πŸ“¦ where this page comes from