__iucv_message_send(9)

📦 version 7.3.1, in nixpkgs unstable

💌 __iucv_message_send(9) — Kernel API Manual, bestie edition 🌸

okay so real talk, this is __iucv_message_send from the Kernel API Manual, and she's the "send it and dip" queen of the IUCV world 👑 — one-way message, zero locking, no replies, no strings. live laugh transmit 💅

✨ NAME ✨

__iucv_message_send — transmits a one-way message, no locking 🦋

🎀 SYNOPSIS 🎀

int __iucv_message_send (struct iucv_path *path , struct iucv_message
*msg , u8 flags , u32 srccls , void *buffer , size_t size );

like literally just hand her a path, a message, some flags and a buffer and she's off 🫶

🧚 ARGUMENTS 🧚

  • path — address of the iucv_path structure 💫 the ride she's taking
  • msg — address of the iucv_message structure, the lil envelope itself
  • flags — how the message is sent (IUCV_IPRMDATA, IUCV_IPPRTY, IUCV_IPBUFLST) 🚩 pick your vibe
  • srccls — source class of message, yep that's a u32
  • buffer — address of send buffer or address of struct iucv_array 👀 two moods, one argument
  • size — length of send buffer, a size_t, keep it honest

💖 DESCRIPTION 💖

This function transmits data to another application. Data to be transmitted is in a buffer and this is a one-way message — the receiver will not reply to the message. it's giving "sent from my iucv" with read receipts permanently off 😭🙈

Locking: no locking. not a crumb of it. ngl she trusts you to handle that yourself 🔥

⭐ RETURN ⭐

the result from the CP IUCV call 🫡 no cap, that's it, that's the return value

🌈 SEE ALSO 🌈

Kernel file ./net/iucv/iucv.c and honestly the whole iucv extended family, come meet them 👑

bestie reminder: no locking means you bring the locking. she said what she said 💀

and that's the page fr fr 🎀 source: ./net/iucv, dated October 2026 — mwah, go send some one-way messages, ily, bye 🫶💜

📦 where this page comes from