mptcp_token_iter_next(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mptcp_token_iter_next β€” kernel API manual, but make it make sense

okay so bestie, this one's a kernel function from the MPTCP token container, and the vibe is: you're walking through a container of tokens, one socket at a time, and this function hands you the next one. it's giving tour guide energy 🧚


✨ NAME ✨

mptcp_token_iter_next β€” iterate over the token container from given pos πŸŽ€


🌸 SYNOPSIS 🌸

struct mptcp_sock * mptcp_token_iter_next (const struct net *net , long
*s_slot , long *s_num );

like literally that's the whole signature, no cap πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • net β€” the namespace you're iterating over. that's the world you're walking through, bestie 🌍
  • s_slot β€” the start slot number. where you're starting your little stroll πŸ‘‘
  • s_num β€” the start number inside the given lock. yes, that's what it says, i'm just relaying the message 🫢

πŸ’– DESCRIPTION πŸ’–

so on a successful iteration, two things happen, and you need to know both:

  • the iterator gets moved to the next position ➑️
  • a reference to the returned socket is acquired πŸ”₯

that reference part is the main character energy here β€” don't sleep on it 😭


⭐ RETURN ⭐

the first mptcp connection structure found inside the token container, starting from the specified position. and if there's nothing there? NULL. that's it, that's the whole answer πŸ’€


🌈 SEE ALSO 🌈

kernel file ./net/mptcp/token.c plus the whole token friend group, all iconic, all linked:


ngl this one's short but she's got range β€” iterate responsibly and remember that reference gets acquired, so act accordingly πŸ™ˆ

and that's a wrap, bestie πŸŽ€ this page lives under ./net/mptcp, dated October 2026, and it slayed every bit of the way πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from