skb_push(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

okay so this is the skb_push(9) page from the Kernel API Manual, and bestie, it’s short but it’s iconic. The whole serve: skb_push β€” add data to the start of a buffer. No cap. πŸ’…


✨ SYNOPSIS ✨

This is the entire synopsis, crystal clear, fr fr:

void * skb_push (struct sk_buff *skb , unsigned int len );

πŸŽ€ ARGUMENTS πŸŽ€

  • skb β€” the buffer to use, bestie. That’s the one we’re working with. 🫢
  • len β€” the amount of data to add. Yep, that many bytes of extra-data energy. ✨

πŸ’– DESCRIPTION πŸ’–

So here’s the vibe: this function extends the used data area of the buffer at the buffer start. It’s giving β€œmake room at the front,” lowkey. πŸ¦‹

⚠️ Important, no cap: if this would exceed the total buffer headroom, the kernel will panic. Like, actual kernel panic. Not a vibe check. Not a cute little warning. Panic. πŸ’€

A pointer to the first byte of the extra data is returned. That’s the return value, bestie β€” void *, first byte of the extra data. Periodt. πŸ‘‘


πŸ¦‹ SEE ALSO πŸ¦‹

Okay so the SEE ALSO section ate and left no crumbs β€” here’s the whole squad, every single one, exactly as listed. 🌈


xoxo, your kernel bestie 🫢 β€” source/version: ./net/core, date: October 2026, and yes bestie, this is the skb_push(9) page from the Kernel API Manual. periodt. πŸ’œ

πŸ“¦ where this page comes from