dfac4f3593
While the patch gives bdrv_graph_wrlock() as an example where the issue can manifest, something similar can happen even when that is disabled. Was able to reproduce the issue with while true; do qm resize 115 scsi0 +4M; sleep 1; done while running fio --name=make-mirror-work --size=100M --direct=1 --rw=randwrite \ --bs=4k --ioengine=psync --numjobs=5 --runtime=1200 --time_based in the VM. Fix picked up from: https://lists.nongnu.org/archive/html/qemu-devel/2023-12/msg01102.html Signed-off-by: Fiona Ebner <f.ebner@proxmox.com> |
||
|---|---|---|
| .. | ||
| 0001-monitor-qmp-fix-race-with-clients-disconnecting-earl.patch | ||
| 0002-scsi-megasas-Internal-cdbs-have-16-byte-length.patch | ||
| 0003-ide-avoid-potential-deadlock-when-draining-during-tr.patch | ||
| 0004-migration-block-dirty-bitmap-fix-loading-bitmap-when.patch | ||
| 0005-hw-ide-reset-cancel-async-DMA-operation-before-reset.patch | ||
| 0006-Revert-Revert-graph-lock-Disable-locking-for-now.patch | ||
| 0007-migration-states-workaround-snapshot-performance-reg.patch | ||
| 0008-Revert-x86-acpi-workaround-Windows-not-handling-name.patch | ||
| 0009-hw-ide-ahci-fix-legacy-software-reset.patch | ||
| 0010-ui-vnc-clipboard-fix-inflate_buffer.patch | ||
| 0011-block-Fix-AioContext-locking-in-qmp_block_resize.patch | ||