batadv_recv_frag_packet(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to the Kernel API Manual page for batadv_recv_frag_packet(9) β€” yes, the manual name is folded in right here at the top, no boring header line needed πŸ’–

🌸 NAME 🌸

batadv_recv_frag_packet β€” process received fragment. That's the whole vibe: it handles a fragment that just showed up. πŸ¦‹

✨ SYNOPSIS ✨

Here's the signature, copied exactly so you can trust it:

int batadv_recv_frag_packet (struct sk_buff *skb , struct batadv_hard_iface *recv_if );

πŸŽ€ ARGUMENTS πŸŽ€

  • skb β€” the received fragment. This is the packet-ish thing being handed over.
  • recv_if β€” interface that the skb is received on. Like the doorway it came through.

πŸ”₯ DESCRIPTION πŸ”₯

okay so this function is lowkey a three-way choose-your-own-adventure, and it does one of exactly three things:

  1. Forward fragment β€” if the assembled packet will exceed our MTU, it forwards the fragment.
  2. Buffer fragment β€” if we still lack further fragments, it buffers the fragment.
  3. Merge fragments β€” if we have all needed parts, it merges the fragments.

πŸ’… RETURN πŸ’…

NET_RX_SUCCESS on success, or NET_RX_DROP in case of failure. That's it β€” slay or drop, no in-between. 😭

🌈 SEE ALSO 🌈

Kernel file ./net/batman-adv/routing.c and the whole friend group:


and that's the whole page, bestie 🫢 this cutie came from source/version ./net/batman-adv and is dated October 2026; title stays batadv_recv_frag_packet(9) πŸ’œβœ¨

πŸ“¦ where this page comes from