I can't reproduce this on commit a93ece47fd9edbd4558db24300056c9a57d3bcd4:
# ./qemu-io copy.img -c "aio_write 9233408 28160"
can't open device copy.img: Could not open backing file: Could not open 'backing_img.file': No such file or directory
and on the latest commit, I get a different error that makes me suspect this has been fixed:
# ./qemu-io copy.img -c "aio_write 9233408 28160"
can't open device copy.img: Image does not contain a reference count table
It just doesn't look as if this was fixed explicitly, as the recent refcount changes reference your other fuzzer disclosures, and not this one.
I can't reproduce this on commit a93ece47fd9edbd 4558db24300056c 9a57d3bcd4:
# ./qemu-io copy.img -c "aio_write 9233408 28160"
can't open device copy.img: Could not open backing file: Could not open 'backing_img.file': No such file or directory
and on the latest commit, I get a different error that makes me suspect this has been fixed:
# ./qemu-io copy.img -c "aio_write 9233408 28160"
can't open device copy.img: Image does not contain a reference count table
It just doesn't look as if this was fixed explicitly, as the recent refcount changes reference your other fuzzer disclosures, and not this one.
...Max?