iptfs_skb_can_add_frags(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

Bestie, we’re on the iptfs_skb_can_add_frags(9) page in the Kernel API Manual, and this one is short but iconic: iptfs_skb_can_add_frags β€” check if ok to add frags from walk to skb. That’s the whole vibe check, no cap.


✨ SYNOPSIS ✨

bool iptfs_skb_can_add_frags (const struct sk_buff *skb , struct
       iptfs_skb_frag_walk *walk , u32 offset , u32 len );

🌸 ARGUMENTS 🌸

  • skb β€” the skb to check for adding frags to. Like, this is the one we’re asking about before we start adding stuff πŸ’…
  • walk β€” the walk that will be used as source for frags. It’s literally the source supply for the frags.
  • offset β€” offset from beginning of original skb to start from. So it tells you where in the original skb this starts from.
  • len β€” amount of data to add frag references to in skb. Basically how much data in the skb is getting frag references added to it.

πŸ’– RETURN πŸ’–

It returns true if ok to add frags. That’s the answer the page gives: true means ok to add frags. Periodt.


πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./net/xfrm/xfrm_iptfs.c, plus the whole friend group:


xoxo, signing off from ./net/xfrm, dated October 2026, on the iptfs_skb_can_add_frags(9) page πŸ’…πŸ«Ά

πŸ“¦ where this page comes from