xenbus_dev_fatal(9)

okay bestie, welcome to xenbus_dev_fatal(9) from the Kernel API Manual. This is the xenbus call that's giving “drop an error message into the store, then shutdown” energy — fatal by name, orderly by nature. 💅

💖 NAME 💖

xenbus_dev_fatal — puts an error message into the store and then shutdown. It's literally the fatal-error bestie for xenbus devices. ✨

✨ SYNOPSIS ✨

void xenbus_dev_fatal (struct xenbus_device *dev , int err , const char
*fmt , ... );

🎀 ARGUMENTS 🎀

• dev — the xenbus device. Main character energy.
• err — the error to report. Spill it.
• fmt — the error message format. This is where the message shape lives.
• ... — variable arguments. The extra lil' args that go with fmt. 🫶

🦋 DESCRIPTION 🦋

okay so this function is equivalent to xenbus_dev_error(dev, err, fmt, args), and then it follows up with xenbus_switch_state(dev, XenbusStateClosing). That second call schedules an orderly closedown of this driver and its peer. So it's giving “report the error, then close down in a coordinated way” energy — no cap. 🔥

🌸 SEE ALSO 🌸

Kernel file: ./drivers/xen/xenbus/xenbus_client.c

• xenbus_watch_path(9)
• xenbus_watch_pathfmt(9)
• xenbus_switch_state(9)
• xenbus_dev_error(9)
• xenbus_map_ring_valloc(9)
• xenbus_unmap_ring(9)
• xenbus_unmap_ring_vfree(9)
• xenbus_read_driver_state(9)

mwah 💋 — this page is signed off from ./drivers/xen/xenbus, dated October 2026, and it's still xenbus_dev_fatal(9) at the end. 🫶