rxrpc_kernel_send_data(9)

💖 rxrpc_kernel_send_data — the Kernel API Manual glow-up ✨

okay so bestie, we're in the Kernel API Manual today and the star of the show is rxrpc_kernel_send_data(9) — literally the function that lets a kernel service yeet data onto a call. strap in 🎀

---

✨ NAME ✨

rxrpc_kernel_send_data — Allow a kernel service to send data on a call 💅

---

🦋 SYNOPSIS 🦋

int rxrpc_kernel_send_data (struct socket *sock , struct rxrpc_call
*call , struct msghdr *msg , size_t len , rxrpc_notify_end_tx_t
notify_end_tx );

---

🌸 ARGUMENTS 🌸

• sock — The socket the call is on. it's giving "which line am I even on" energy 🔌
• call — The call to send data through. this is the main character fr fr 👑
• msg — The data to send. the actual payload, the whole point, the moment 💌
• len — The amount of data to send. how many bytes we're serving today, no cap 📏
• notify_end_tx — Notification that the last packet is queued. like a little "k that was the last one bestie" ping 🛎️

---

🌈 DESCRIPTION 🌈

Allow a kernel service to send data on a call. 🫶

The call must be in an state appropriate to sending data. so like, vibe check first — if the call isn't in the right state, sending is not happening, periodt.

No control data should be supplied in msg, nor should an address be supplied. nope, none, don't even try it 🙈

MSG_MORE should be flagged if there's more data to come — otherwise this data will end the transmission phase. so if you're mid-thought, flag it; if you're done talking, don't, because that last packet literally closes out the whole transmission era 😭

---

⭐ RETURN ⭐

0 if successful and a negative error code otherwise. slay on 0, and if you get a negative number... that's the universe telling you something went wrong 💀

---

🔥 SEE ALSO 🔥

Kernel file ./net/rxrpc/sendmsg.c rxrpc_kernel_abort_call(9), rxrpc_kernel_set_tx_length(9)

---

and that's the page!! brought to you by the folks over at ./net/rxrpc, dated October 2026 — mwah, go send some data responsibly bestie 💜🧚‍♀️