rpc_queue_upcall(9)

🌸 NAME 🌸

okay so this is rpc_queue_upcall, straight out of the Kernel API Manual, and it does exactly what it says on the tin, bestie: it queues an upcall message to userspace. iconic behavior, no cap 💅

---

🦋 SYNOPSIS 🦋

int rpc_queue_upcall (struct rpc_pipe *pipe , struct rpc_pipe_msg *msg
);

---

🎀 ARGUMENTS 🎀

• pipe — the upcall pipe on which to queue the given message 🫶
• msg — the message to queue ✨

---

💅 DESCRIPTION 💅

So you call this with an inode created by rpc_mkpipe to queue an upcall. That's the whole vibe.

Then, later, a userspace process may read the upcall — literally by performing a read on an open file for this inode. cute, right? 😌

And listen: it is up to the caller to initialize the fields of msg appropriately. Every field except msg->list, okay? That one is not your problem. The rest? You better have them set up correctly, fr fr 🎀

---

🌈 SEE ALSO 🌈

Kernel file ./net/sunrpc/rpc_pipe.c, and the whole bestie lineup:

• rpc_mkpipe_dentry(9)
• rpc_unlink(9)
• rpc_init_pipe_dir_head(9)
• rpc_init_pipe_dir_object(9)
• rpc_add_pipe_dir_object(9)
• rpc_remove_pipe_dir_object(9)
• rpc_find_or_alloc_pipe_dir_object(9)
• rpc_create_client_dir(9)
• rpc_remove_client_dir(9)
• rpc_gssd_dummy_populate(9)

---

okay bye bestie, this was rpc_queue_upcall(9) from source/version ./net/sunrpc, dated October 2026 — periodt 💖✨