cio_cancel_halt_clear(9)

💖 NAME 💖

cio_cancel_halt_clear — cancel running I/O by performing cancel, halt, and clear ordinally if the subchannel is valid. 🫶

okay bestie, this page is cio_cancel_halt_clear(9) from the Kernel API Manual, and it's giving very specific cleanup energy. 💅

✨ SYNOPSIS ✨

int cio_cancel_halt_clear (struct subchannel *sch , int *iretry );

🎀 ARGUMENTS 🎀

• sch — the subchannel on which to perform the cancel_halt_clear operation. 🦋
• iretry — the number of the times remained to retry the next operation. 😭

🔥 DESCRIPTION 🔥

This should be called repeatedly since halt/clear are asynchronous operations. We do one try with cio_cancel, three tries with cio_halt, and 255 tries with cio_clear. The caller should initialize iretry with the value 255 for its first call to this, and keep using the same iretry in the subsequent calls until it gets a non -EBUSY return. ⭐

Returns:

• 0 if device now idle 👑
• -ENODEV for device not operational 💀
• -EBUSY if an interrupt is expected (either from halt/clear or from a status pending) 🙈
• -EIO if out of retries. 😭

🌈 SEE ALSO 🌈

• Kernel file ./drivers/s390/cio/cio.c
• cio_update_schib(9)
• cio_enable_subchannel(9)
• cio_disable_subchannel(9)
• cio_tm_start_key(9)
• cio_tm_intrg(9)

mwah 💖 this iconic page comes from the source/version ./drivers/s390/cio, dated October 2026, and it's literally cio_cancel_halt_clear(9). periodt. 🎀