aboutsummaryrefslogtreecommitdiff
path: root/hw/scsi/virtio-scsi-dataplane.c
diff options
context:
space:
mode:
authorKevin Wolf <kwolf@redhat.com>2023-12-01 15:25:18 +0100
committerKevin Wolf <kwolf@redhat.com>2023-12-21 22:49:27 +0100
commitd3007d348adaaf04ee8b099a475282034a662414 (patch)
tree15d0444ad44f4f6e9b1a59948907136b6c8e7f1e /hw/scsi/virtio-scsi-dataplane.c
parent6b5aa3a0fdfc74d42f9f7705fa6ced73253b06b1 (diff)
downloadqemu-d3007d348adaaf04ee8b099a475282034a662414.zip
qemu-d3007d348adaaf04ee8b099a475282034a662414.tar.gz
qemu-d3007d348adaaf04ee8b099a475282034a662414.tar.bz2
block: Fix crash when loading snapshot on inactive node
bdrv_is_read_only() only checks if the node is configured to be read-only eventually, but even if it returns false, writing to the node may not be permitted at the moment (because it's inactive). bdrv_is_writable() checks that the node can be written to right now, and this is what the snapshot operations really need. Change bdrv_can_snapshot() to use bdrv_is_writable() to fix crashes like the following: $ ./qemu-system-x86_64 -hda /tmp/test.qcow2 -loadvm foo -incoming defer qemu-system-x86_64: ../block/io.c:1990: int bdrv_co_write_req_prepare(BdrvChild *, int64_t, int64_t, BdrvTrackedRequest *, int): Assertion `!(bs->open_flags & BDRV_O_INACTIVE)' failed. The resulting error message after this patch isn't perfect yet, but at least it doesn't crash any more: $ ./qemu-system-x86_64 -hda /tmp/test.qcow2 -loadvm foo -incoming defer qemu-system-x86_64: Device 'ide0-hd0' is writable but does not support snapshots Signed-off-by: Kevin Wolf <kwolf@redhat.com> Message-ID: <20231201142520.32255-2-kwolf@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'hw/scsi/virtio-scsi-dataplane.c')
0 files changed, 0 insertions, 0 deletions