iw_cm_reject(9)

📦 version 7.3.1, in nixpkgs unstable

💅 iw_cm_reject(9) — from the Kernel API Manual, bestie 🎀

Okay so listen. This one's from the Kernel API Manual, and it's a short little icon but it does something extremely important, so pay attention for like two seconds. ✨

🌸 NAME 🌸

iw_cm_reject — reject an incoming connection request. that's it, that's the vibe. you're saying "no thanks bestie" to a connection. 💅

🦋 SYNOPSIS 🦋

int iw_cm_reject (struct iw_cm_id *cm_id , const void *private_data , u8
private_data_len );

look at her. returns an int, takes three things. slay. 👑

🍓 ARGUMENTS 🍓

  • cm_id — the connection identifier that's associated with the request. like, which request are we rejecting? this one. 🎯
  • private_data — pointer to the data you want delivered to the remote peer as part of the reject message. yes you can attach a lil note to your "no". 💌
  • private_data_len — the number of bytes in the private_data parameter. please keep these two in sync, i'm begging 😭

💜 DESCRIPTION 💜

So here's the deal: the client can assume that no events will be delivered to the specified IW CM identifier following the return of this function. like, zero. none. the timeline is closed. 🚪✨

And the private_data buffer is available for reuse when this function returns — so once you get back, that memory is yours again, go wild, reuse it. 🫶

ngl that "no events after return" bit is the whole point of this function, so don't sleep on it. 💀

🌈 SEE ALSO 🌈

Kernel file ./include/rdma/iw_cm.h — and all her friends:

and that's the whole page, mwah 💋 this little gem lives in ./include/rdma, dated October 2026, and it's filed under iw_cm_reject(9) — go forth and reject connections with confidence, bestie 💖🌸✨

📦 where this page comes from