Gauthier Jolly 3d78662498 block: virtio-blk: report IO errors to the guest ... Instead of exiting on IO errors, report the errors to the guest with VIRTIO_BLK_S_IOERR. For example, the guest kernel will log something similar to this if the nbd behind /dev/vdc is unexpectedly disconnected: [ 166.033957] I/O error, dev vdc, sector 264 op 0x1:(WRITE) flags 0x9800 phys_seg 1 prio class 2 [ 166.035083] Aborting journal on device vdc-8. [ 166.037307] Buffer I/O error on dev vdc, logical block 9, lost sync page write [ 166.038471] JBD2: I/O error when updating journal superblock for vdc-8. [...] [ 174.234470] EXT4-fs (vdc): I/O error while writing superblock In case the rootfs is not located on the affected block device, this will not crash the guest. Fixes: #6995 Signed-off-by: Gauthier Jolly <contact@gjolly.fr>		2025-06-09 16:48:07 +00:00
..
src	block: virtio-blk: report IO errors to the guest	2025-06-09 16:48:07 +00:00
build.rs	build: Add "fuzzing" as a valid cfg(..) attribute	2024-05-08 08:10:28 +00:00
Cargo.toml	misc: streamline thiserror cargo dep	2025-05-28 17:24:34 +00:00