pskb_put(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, this is pskb_put(9) from the Kernel API Manual, and it's giving β€œadd data to the tail of a potentially fragmented buffer” with zero chill. let's go πŸ’…βœ¨

πŸ’– NAME πŸ’–

pskb_put β€” add data to the tail of a potentially fragmented buffer. no cap, that's the whole name, and it ate.

✨ SYNOPSIS ✨

void * pskb_put (struct sk_buff *skb , struct sk_buff *tail , int len );

πŸŽ€ ARGUMENTS πŸŽ€

  • skb β€” start of the buffer to use. your main character buffer, basically.
  • tail β€” tail fragment of the buffer to use. the final-fragment bestie.
  • len β€” amount of data to add. the size of the extra data moment.

πŸ¦‹ DESCRIPTION πŸ¦‹

so this function extends the used data area of the potentially fragmented buffer. yes, the whole β€œfragmented” situation is the point β€” it's not scared of a buffer that's split into pieces. πŸ’…

real talk: tail must be the last fragment of skb -- or skb itself. like, not a random middle fragment, not your ex, not some other buffer. the last one, or the og. iykyk.

⚠️ if this would exceed the total buffer size, the kernel will panic. not a cute little error, not a vibe check, an actual panic. so maybe don't do that, bestie 😭

and the payoff? a pointer to the first byte of the extra data is returned. periodt. 🫢

🌈 SEE ALSO 🌈

Kernel file ./net/core/skbuff.c β€” plus the whole skb cinematic universe, fr fr:


okay that's the whole page, bestie. source/version: ./net/core; date: October 2026; manual page: pskb_put(9). bye, slay, hydrate, and don't overflow the buffer πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from