batadv_bla_process_claim(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ batadv_bla_process_claim(9) β€” the kernel API manual, but make it make sense

okay so bestie, this one's from the Kernel API Manual (section 9, kernel-space girlies only πŸ’…) and it's literally all about batadv_bla_process_claim β€” checking whether the frame you're holding is a claim frame and, if it is, processing it. iconic behavior honestly.


✨ NAME ✨

batadv_bla_process_claim β€” check if this is a claim frame, and process it πŸŽ€


🌸 SYNOPSIS 🌸

bool batadv_bla_process_claim (struct batadv_priv *bat_priv , struct
batadv_hard_iface *primary_if , struct sk_buff *skb );

like, returns a bool, takes three things, no cap. 🫢


πŸ’– ARGUMENTS πŸ’–

  • bat_priv β€” the bat priv holding all the mesh interface info. it's giving "the main character struct" πŸ‘‘
  • primary_if β€” the primary hard interface of this batman mesh interface. yes, this one, the primary one πŸ¦‹
  • skb β€” the frame that's getting checked. this is the one on trial, bestie πŸ™ˆ

⚠️ DESCRIPTION ⚠️

Warning: this function may reallocate the skb data buffer via batadv_get_vid/...

and like, that's the whole thing you need to know, because any pointer into the skb data β€” think anything you got from skb->data or eth_hdr before you called this β€” must be considered invalid afterwards. literally do not trust it. πŸ’€ you have to reacquire it. no stashing old pointers, that's not the vibe, that's a bug. ✨


πŸ”₯ RETURN πŸ”₯

  • true β€” slay, it was a claim frame 🌈
  • false β€” nope, not a claim frame, and this is you telling the callee it can go ahead and use the frame on its own 🫢

πŸ’œ SEE ALSO πŸ’œ

that's a lot of cross-references and honestly? obsessed. go read them all, bestie, they're literally all in the BLA squad 🧚


mwah πŸ’‹ this page lives in ./net/batman-adv and the version/date stamp on it is October 2026 β€” yes, the future, and no, we're not explaining that. it's giving time traveler energy πŸ•°οΈβœ¨ periodt.

πŸ“¦ where this page comes from