__skb_ext_alloc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– __skb_ext_alloc(9) β€” Kernel API Manual πŸ’–

okay bestie, welcome to the Kernel API Manual ✨. We're talking about __skb_ext_alloc β€” yes, she has a dramatic number of underscores, and honestly? Iconic.

🌟 NAME 🌟

__skb_ext_alloc β€” allocate a new skb extensions storage πŸŽ€

πŸŽ€ SYNOPSIS πŸŽ€

struct skb_ext * __skb_ext_alloc (gfp_t flags );

🌸 ARGUMENTS 🌸

  • flags β€” for the details, the manual literally says β€œSee kmalloc.” That's the whole pointer, bestie. Go check kmalloc for the flags lore πŸ’….

πŸ¦‹ DESCRIPTION πŸ¦‹

This one returns the newly allocated pointer. That pointer can later be attached to a skb via __skb_ext_set. So it's giving β€œallocate now, attach later” β€” very main character energy πŸ”₯.

🫢 NOTE 🫢

The caller must handle the skb_ext as opaque data. No peeking inside, no vibe-checking its internals β€” opaque means opaque, periodt. 🫢

πŸ’œ SEE ALSO πŸ’œ

The original points at the kernel file ./net/core/skbuff.c and then name-drops this entire group chat:


mwah πŸ’‹ β€” brought to you by the ./net/core source/version, dated October 2026, and the page __skb_ext_alloc(9). byeee πŸ¦‹

πŸ“¦ where this page comes from