rdma_consumer_reject_data(9)

💅 rdma_consumer_reject_data(9) 💅

okay so bestie, welcome to the Kernel API Manual — yes this is a section 9 page, iykyk, we're in kernel-internals territory 🧚✨ pull up a chair.

---

✨ NAME ✨

rdma_consumer_reject_data — literally just hands you back the consumer reject private data and its length, if there even is any 🎀

---

🌸 SYNOPSIS 🌸

const void * rdma_consumer_reject_data (struct rdma_cm_id *id , struct rdma_cm_event *ev , u8 *data_len );

that's the whole vibe. three args, one pointer back, no cap 💅

---

🦋 ARGUMENTS 🦋

• id — the communication identifier that received the REJECT event 👑 like, this is the one who got rejected, be nice to it.
• ev — the RDMA CM reject event itself. the actual rejection, in event form 💀
• data_len — a pointer to the resulting length of the consumer data. so you pass in a pointer and it gets filled with the length — the data itself stays over there, the length comes back here 🫶

---

💖 SEE ALSO 💖

the kernel file lives at ./include/rdma/rdma_cm.h — iconic header, no notes ✨ and then there's the whole friend group:

rdma_create_id(9), rdma_destroy_id(9), rdma_restrict_node_type(9), rdma_bind_addr(9), rdma_resolve_addr(9), rdma_resolve_route(9), rdma_resolve_ib_service(9), rdma_create_qp(9), rdma_destroy_qp(9), rdma_init_qp_attr(9), rdma_listen(9), rdma_notify(9), rdma_reject(9), rdma_disconnect(9), rdma_join_multicast(9), rdma_leave_multicast(9), rdma_set_service_type(9), rdma_set_reuseaddr(9), rdma_set_afonly(9), rdma_reject_msg(9), rdma_read_gids(9)

twenty of them fr fr, go read the whole set, it's giving complete education 🌈📚

---

quick vibe check: there's genuinely no DESCRIPTION section on this one and no RETURN VALUE either — the manpage just says what it says, so i'm not out here inventing lore 🙈 what you see is what you get.

---

anyway that's the page!! mwah 💋 this one's served up from ./include/rdma, dated October 2026, and yeah it's still rdma_consumer_reject_data(9) — same girl, same manual, staying iconic 🌟