iucv_path_sever(9)
πΈ NAME πΈ
iucv_path_sever β bestie, this is the function that Terminates an IUCV path. literally hanging up the phone on your communication partner, no cap π
This page is from the Kernel API Manual, and it's giving very much "we're so done here" energy π«Ά
β¨ SYNOPSIS β¨
int iucv_path_sever (struct iucv_path *path , u8 *userdata );
okay so the whole vibe: you give it an int back, you hand it a struct iucv_path * and a u8 *, and it goes off and severs the path π₯
π ARGUMENTS π
pathβ the address of theiucv_pathstructure. this is the main character right here, the actual path you're about to sever πuserdataβ 16 bytes of data, and those babies get reflected to the communication partner. yes bestie, 16, exactly 16, don't come at me with 15 π π
π₯ RETURN π₯
- it returns the result from the CP IUCV call. that's it, that's the tea π β whatever the CP IUCV call hands back is literally what you get.
π¦ SEE ALSO π¦
π§ psa: the kernel file ./net/iucv/iucv.c is where all the magic lives β go say hi β¨
__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_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)
mwah π go sever those paths, queen π
this lil page came from ./net/iucv, dated October 2026, and it's iucv_path_sever(9) all day every day ππ
π¦ 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