__llc_lookup_established(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… __llc_lookup_established(9) β€” bestie's guide to finding a connection πŸ’…

okay so you're reading __llc_lookup_established(9) from the Kernel API Manual, and honestly? it's a little baddie with one job and it does it flawlessly. let's get into it 🫢


✨ NAME ✨

__llc_lookup_established β€” finds the connection for the remote/local sap/mac 🌸

literally what it says on the tin. it goes looking for a connection, using the remote and local sap/mac combo. no cap.


πŸ¦‹ SYNOPSIS πŸ¦‹

struct sock * __llc_lookup_established (struct llc_sap *sap , struct llc_addr *daddr , struct llc_addr *laddr , const struct net *net );

πŸŽ€ ARGUMENTS πŸŽ€

  • sap β€” the SAP. that's the service access point, bestie πŸ’–
  • daddr β€” the address of the remote LLC (that's MAC + SAP, both of 'em) ✨
  • laddr β€” the address of the local LLC (again, MAC + SAP) πŸ¦‹
  • net β€” the netns to look up a socket in 🌈

πŸ”₯ DESCRIPTION πŸ”₯

so the way that this works 😭 β€” it searches the connection list of the SAP and finds the connection using the remote mac, the remote sap, the local mac, and the local sap. all four. it's thorough like that πŸ’…

if it finds the connection? you get a pointer to it, slay πŸ‘‘. if it doesn't? you get NULL, and that's just how it is πŸ™ˆ

⚠️ heads up bestie: the caller has to make sure local_bh is disabled. not optional, not a vibe, it's the rule 🚨

πŸ’œ SEE ALSO πŸ’œ

all the siblings in the Kernel file ./net/llc/llc_conn.c β€” go say hi to the whole fam 🫢


and that's the whole page, periodt πŸ’– this one came to you from ./net/llc, dated October 2026, and it's all about __llc_lookup_established(9) β€” iykyk ⭐🧚

πŸ“¦ where this page comes from