rxrpc_kernel_dequeue_oob(9)

✨ NAME ✨

rxrpc_kernel_dequeue_oob — Dequeue and return the front OOB message

Okay bestie, this is the rxrpc_kernel_dequeue_oob(9) page from the Kernel API Manual, and we're about to make kernel queue behavior make sense. This one is literally all about pulling the front OOB message and handing it back to you. 💅

🌸 SYNOPSIS 🌸

struct sk_buff * rxrpc_kernel_dequeue_oob (struct socket *sock , enum
rxrpc_oob_type *_type );

🎀 ARGUMENTS 🎀

• sock — The socket to query. It's the socket you're asking, bestie.
• _type — Where to return the message type. This is the spot where the type gets handed back to you.

🦋 DESCRIPTION 🦋

Dequeue the front OOB message, if there is one, and return it and its type. That's the whole mood — if there's a message sitting at the front of the OOB queue, this takes it and gives you both the message and its type. No cap. ✨

👑 RETURN 👑

The sk_buff representing the OOB message, or NULL if the queue was empty. So if you get NULL, bestie, the queue was empty — that's the vibe check. 💀

💜 SEE ALSO 💜

Kernel file ./net/rxrpc/oob.c, plus these other pages:

• rxrpc_kernel_query_oob(9)
• rxrpc_kernel_free_oob(9)
• rxrpc_kernel_query_challenge(9)
• rxrpc_kernel_reject_challenge(9)

That's the whole page, bestie. Source/version: ./net/rxrpc; date: October 2026. rxrpc_kernel_dequeue_oob(9) signing off — mwah 💋✨