__iucv_message_receive(9)
πΈ __iucv_message_receive (9) β Kernel API Manual π
okay so bestie, welcome to the Kernel API Manual, section 9, and today's main character is __iucv_message_receive. she receives messages. she does NOT do locking. we stan a low-maintenance icon β¨
β¨ NAME β¨
__iucv_message_receive β Receives messages on an established path (no locking) π
like yes, that's the whole vibe: messages come in on a path you already established, and she does not lock anything. not her job. not her problem. periodt.
π¦ SYNOPSIS π¦
int __iucv_message_receive (struct iucv_path *path , struct iucv_message
*msg , u8 flags , void *buffer , size_t size , size_t *residual );
look at that signature. gorgeous. iconic. returns an int, takes six whole arguments, and one of them is literally a size_t *residual so you will be getting a pointer back, no cap π
π ARGUMENTS π
pathβ address ofiucv pathstructure. this is your established path, the little road the messages travel on π£οΈmsgβ address ofiucv msgstructure. the message itself lives here π«Άflagsβ flags that affect how the message is received. the one flag named here isIUCV_IPBUFLSTβbufferβ address of data buffer, or address ofstruct iucv_array. yes, she's flexible like that β either a plain buffer or an array struct π₯sizeβ length of data buffer. keep it accurate or, like, don't πresidualβ bestie the original manpage literally gives no description here, so I'm not about to invent one for you. it's a parameter, it's listed, that's what we know π
π DESCRIPTION π
so here's the tea β β this function receives messages that are being sent to you over established paths. that's it, that's the job, and she does it well π
and the extra slay? she will also deal with RMDATA messages embedded in struct iucv_message as well. so those little embedded ones don't get to sneak past her. not on her watch π
Locking: no locking π¨
like, for real, none. so if you were expecting her to hold a lock for you, she is not that girl. you handle that yourself, bestie. iykyk.
π RETURN π
the result from the CP IUCV call. she's not out here making up her own return values, she just hands you back whatever CP IUCV said. honest queen π«Ά
π SEE ALSO π
Kernel file ./net/iucv/iucv.c β and the entire friend group, in order:
__iucv_call_b2f0(9)iucv_allow_cpu(9)iucv_block_cpu(9)iucv_declare_cpu(9)iucv_retrieve_cpu(9)iucv_sever_pathid(9)__iucv_cleanup_queue(9)iucv_cleanup_queue(9)iucv_register(9)iucv_unregister(9)iucv_path_accept(9)iucv_path_connect(9)iucv_path_quiesce(9)iucv_path_resume(9)iucv_path_sever(9)iucv_message_purge(9)iucv_message_receive_iprmdata(9)iucv_message_receive(9)iucv_message_reject(9)iucv_message_reply(9)__iucv_message_send(9)iucv_message_send(9)iucv_message_send2way(9)iucv_path_pending(9)iucv_path_complete(9)iucv_path_severed(9)iucv_path_quiesced(9)iucv_path_resumed(9)iucv_message_complete(9)iucv_message_pending(9)iucv_init(9)iucv_exit(9)
like, the whole roster. she knows everybody π¦
and that's a wrap, bestie π this page came from ./net/iucv, dated October 2026, and it's filed under __iucv_message_receive(9) β go forth and receive those messages, no locking, no stress, all vibes πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms