iucv_path_accept(9)
π iucv_path_accept(9) π
okay so bestie, welcome to the Kernel API Manual β yes that's the manual name, we're in kernel land now, put your big-girl glasses on π β and today's main character is iucv_path_accept, the little function that says "yes bestie, let's talk" to an IUCV path β¨
πΈ NAME πΈ
iucv_path_accept β Complete the IUCV communication path π«Ά
no like literally, that's the whole job. completing the path. slay.
β¨ SYNOPSIS β¨
int iucv_path_accept (struct iucv_path *path , struct iucv_handler
*handler , u8 *userdata , void *private );
π ARGUMENTS π
pathβ the address of theiucv_pathstructure. this is the vibe, the whole situation, the path in question πhandlerβ the address of theiucv_handlerstructure. your handler bestie, the one holding it downuserdataβ 16 bytes of data that gets reflected to the communication partner π yes exactly sixteen, count them, no cap. it's giving "here's a lil something about me" energyprivateβ private data that gets passed to the interrupt handlers for this path π your own lil secret, just for this path, iykyk
π¦ DESCRIPTION π¦
so the way that this works is, this function gets issued after the user received a connection pending external interrupt β like, the interrupt already showed up and said "hey someone wants to connect" β and now the user wishes to complete the IUCV communication path π«
that's it. that's the moment. you got the interrupt, you're like "okay sure, let's do this", and iucv_path_accept is the function that makes it official. main character energy fr fr π₯
β RETURN β
returns the result of the CP IUCV call β like, whatever CP says, that's what you get. no extra interpretation, no sugar-coating, just the raw result straight from the call π
π SEE ALSO π
Kernel file ./net/iucv/iucv.c β plus the whole friend group, they all showed up:
__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_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_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)
and that's the whole page bestie, go forth and complete those paths π
also lowkey: this lives in./net/iucvand it's the October 2026 edition ofiucv_path_accept(9)β so like, keep that in mind, timeline-wise π°οΈβ¨
iucv_path_accept(9) β periodt. π
π¦ 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