llc_build_and_send_xid_pkt(9)

📦 version 7.3.1, in nixpkgs unstable

💅 llc_build_and_send_xid_pkt(9) — from the Kernel API Manual 🎀

okay so bestie, pull up a chair, because this one's a little function with main character energy in the LLC (Logical Link Control) world. It's the XID interface for upper layers — that's the NAME section, and yes we're keeping it ✨

🌸 SYNOPSIS 🌸

void llc_build_and_send_xid_pkt (struct llc_sap *sap , struct sk_buff
*skb , u8 *dmac , u8 dsap );

not me copying that exactly as written, line break and all, because the facts are sacred even when the formatting is giving "wrote this at 3am" 😭💀

🫶 ARGUMENTS 🫶

four args, all of them important, none of them optional, let's go 💖

  • sap — the sap to use. that's your Service Access Point, the whole reason this function can do its thing 🧚
  • skb — the packet to send. your sk_buff, your moment, your payload 👑
  • dmac — destination mac address. where it's going, fr fr 🦋
  • dsap — destination sap. where it's going logically, iykyk ⭐

💜 DESCRIPTION 💜

so here's the vibe: this function gets called when an upper layer wants to send a XID pdu. that's it, that's the whole gig, no cap 🌈

and then — okay this is my favorite part — the manpage says it returns 0 for success, 1 otherwise. which is iconic of it. and also, if you scroll back up to the SYNOPSIS, it's declared void. so the docs are out here giving "both things are true" 💀 i'm just telling you what the page says, bestie, i'm not here to litigate it 🙈

🔥 SEE ALSO 🔥

the whole friend group, assembles 🌸

quick vibe check before you go: everything above is exactly what the page says. don't come for me if the return value situation confuses you — i simply reported it with love 🩷

and that's the whole page, diva 💅 it lives under ./net/llc, dated October 2026, all official in the Kernel API Manual. mwah, go send some XID pdus 🎀💖

📦 where this page comes from