iucv_path_severed(9)

💅 iucv_path_severed(9) — like, the kernel API manual, bestie

Ok so real talk, this is a page from the Kernel API Manual (section 9, the "kernel internals" girlies) and it's all about one tiny function that handles the ✨connection severed✨ work item. Short page, but she's important, iykyk 🎀

---

🌸 NAME 🌸

iucv_path_severed — process the connection severed work item. That's it, that's the whole gig 💅

---

⭐ SYNOPSIS ⭐

void iucv_path_severed (struct iucv_irq_data *data );

Returns nothing (void), takes one pointer, no cap 🫶

---

🦋 ARGUMENTS 🦋

• data — a pointer to the external interrupt buffer. That's literally the whole arg list, she travels light ✨

---

🔥 CONTEXT 🔥

So where does this even run? It gets called from a tasklet while holding iucv_table_lock — so yeah, you're in that locked-up context, act accordingly bestie 😭🔒

---

👑 SEE ALSO 👑

Kernel file ./net/iucv/iucv.c — and like, the entire friend group, honestly 🌈

• __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_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_quiesced(9), iucv_path_resumed(9)
• iucv_message_complete(9), iucv_message_pending(9)
• iucv_init(9), iucv_exit(9)

Yeah, that's the whole crew — 32 entries and not one of them is getting left out, periodt 💜

---

Ok bye bestie, go sever some paths (the function does it, not you, please don't) 🧚‍♀️💖

This iconic little number comes to you straight out of ./net/iucv, stamped October 2026 — slay, see you in the next release 🌸