tipc_sk_filtering(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– tipc_sk_filtering πŸ’–

okay so this is a page from the Kernel API Manual β€” yes bestie, the kernel has lore too β€” and it's all about tipc_sk_filtering, a lil function whose whole job is checking whether a socket should be traced. that's it. that's the vibe. πŸŽ€


✨ SYNOPSIS ✨

bool tipc_sk_filtering (struct sock *sk );

literally one argument, returns a bool, we love a low-maintenance king πŸ‘‘


🌸 ARGUMENTS 🌸

  • sk β€” the socket to be examined πŸ‘€ that's the one getting the vibe check

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea: sysctl_tipc_sk_filter gets used as the socket tuple for filtering. and that tuple is made of these five things, in this exact order:

  • portid
  • sock type
  • name type
  • name lower
  • name upper

that's the whole description, no cap. the sysctl is the tuple, the tuple is the filter, periodt. πŸ’…


πŸ’œ RETURN πŸ’œ

it hands back true if the socket meets the socket tuple data β€” and quick note, a value of 0 means 'any' ✨ β€” or when there is no tuple set at all (that's all = 0). otherwise? false. simple as. 🫢


🌈 SEE ALSO 🌈

buckle up bestie, this list is LONG and honestly iconic for it. iykyk:

forty-two refs, tenderly hand-counted, zero skipped, we do NOT skip entries in this house πŸ§šβ€β™€οΈπŸ”₯


ok real talk: nothing here is scary, but don't go inventing tuple values in your head β€” 0 means 'any' and no tuple set is all = 0, and that's exactly what the page says, so keep it that way πŸ™ˆ

and that's the whole page, bestie, slay πŸ’… source is ./net/tipc, dated October 2026, and yes it's filed under the manual name Kernel API Manual β€” catch you in the next one, muah πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from