rxrpc_kernel_query_oob(9)

🦋 rxrpc_kernel_query_oob(9) — like, the Kernel API Manual, bestie 🦋

okay so picture this: it's a kernel API manual page, the vibe is immaculate, and this one function is the main character. let's get into it 💅

---

✨ NAME ✨

rxrpc_kernel_query_oob — bestie, it queries the parameters of an out-of-band message. that's it, that's the whole job 🎀

---

🌸 SYNOPSIS 🌸

enum rxrpc_oob_type rxrpc_kernel_query_oob (struct sk_buff *oob , struct rxrpc_peer **_peer , unsigned long *_peer_appdata );

so yeah, that's the whole signature, no cap. it hands you back an enum rxrpc_oob_type and takes three things. scroll down, i'll explain 💖

---

💜 ARGUMENTS 💜

• oob — the message you want to query, babe. that's the one. 👀
• _peer — this is where you return the peer record. like, you pass in the spot and it gets filled in. iconic behaviour honestly.
• _peer_appdata — the application data attached to a peer record. that's the vibe. that's what it is. 🫶

---

🔥 DESCRIPTION 🔥

okay so the whole point: you extract useful parameters from an out-of-band message. ✨

the source peer parameters get returned through the argument list (yes, through the list, that's how it works, don't come for me) and the message type is what comes back as the return value. so you get the peer deets and the type. two for one. slay. 👑

---

⭐ RETURN ⭐

• RXRPC_OOB_CHALLENGE — a challenge wanting a response. it's giving "your move" energy fr fr 💀

---

🌈 SEE ALSO 🌈

kernel file ./net/rxrpc/oob.c plus its little friend group: rxrpc_kernel_dequeue_oob(9), rxrpc_kernel_free_oob(9), rxrpc_kernel_query_challenge(9), rxrpc_kernel_reject_challenge(9) 🧚‍♀️

---

and that's the page, bestie!! this whole thing lives in ./net/rxrpc, it's dated October 2026, and it's filed under rxrpc_kernel_query_oob(9). go query those out-of-band messages. periodt. 💅🌸💖