skb_frag_address(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… skb_frag_address(9)

okay so bestie, welcome to the Kernel API Manual β€” yes this is a real page from it, skb_frag_address(9), and no cap it's actually one of the shorter ones so we're gonna get through it together 🫢


✨ NAME ✨

skb_frag_address β€” gets the address of the data contained in a paged fragment

literally that's the whole job. it hands you a pointer to where the actual bytes live inside a paged fragment. iconic, minimal, does one thing 🌸


πŸŽ€ SYNOPSIS πŸŽ€

void * skb_frag_address (const skb_frag_t *frag );

so it takes one thing and gives you back a void *. that's it. that's the function πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • frag β€” the paged fragment buffer. this is the thing you're asking about. it's const, so like… hands off, we're just looking πŸ‘€

⭐ RETURN ⭐

the address of the data within frag.

⚠️ the page must already be mapped. like, must. this is not a vibe check, it's a requirement β€” if the page isn't mapped yet you don't get a cute answer, you get problems. so map it first, bestie 😭

🌈 SEE ALSO 🌈

okay this is the part where the manpage goes feral and lists, like, everything in the skbuff cinematic universe. but every single one is here, no skipping, we're doing this πŸ‘‘

like I said. cinematic universe. take your time, hydrate, come back to it πŸ“


and that's the whole page!! short, sweet, extremely niche πŸ’œ

🧚 sign-off time: this lil beauty lives under ./include/linux and the date on it is October 2026. bookmark it, cite it, live laugh love it. bye bestie!! πŸ’–βœ¨
πŸ“¦ where this page comes from