skb_postpull_data_move(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ skb_postpull_data_move(9) ✨

okay so bestie, welcome to the Kernel API Manual πŸ’– this one's a little helper from ./include/linux and she's serving serious "I clean up after skb_pull()" energy πŸŽ€


🌸 NAME 🌸

skb_postpull_data_move β€” move packet data and metadata after skb_pull(). that's it, that's the whole job πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

void skb_postpull_data_move (struct sk_buff *skb , const unsigned int
len , const unsigned int n );

✨ ARGUMENTS ✨

  • skb β€” the packet we're operating on 🫢 like, the actual sk_buff in question.
  • len β€” how many bytes got pulled from sk_buff->data. yes, the pull already happened, we're doing the aftermath πŸ’€
  • n β€” how many bytes to memmove from the pre-pull sk_buff->data. so: the before picture, moved forward πŸ”₯

πŸ’œ DESCRIPTION πŸ’œ

literally just go read skb_data_move for the details 😭 she's the main character here, this page is basically her little sister.

no cap, that's the entire description. short and iconic πŸ‘‘


🌈 SEE ALSO 🌈

bestie there are so many siblings, buckle in πŸŽ€ all of these are section (9) and they all live in the kernel file ./include/linux/skbuff.h β€” iykyk:

fr fr go read skb_data_move(9) first, this page is a footnote and she knows it πŸ™ˆ

and that's the whole vibe check, bestie 🧚 this page is from ./include/linux, dated October 2026, and it's serving skb_postpull_data_move(9) realness from the Kernel API Manual β€” slay, bye πŸ’…πŸ’–

πŸ“¦ where this page comes from