On Fri, Oct 25, 2019 at 04:29:15PM +0200, Kevin Wolf wrote: > Hi, > > the QEMU 4.1.0 release has two problems that can easily cause image > corruption with any qcow2 images (no special configuration needed to > trigger the bugs): > > 1. A locking bug in the qcow2 code. I just sent a pull request that > includes the fix for this. The important patch there is: > > 'qcow2: Fix corruption bug in qcow2_detect_metadata_preallocation()' > > 2. A kernel bug in the XFS driver that became visible by new I/O > patterns the qcow2 implementation started to use in 4.1. Max is > currently working on a workaround for this. > > The Planning/4.1 wiki page tells me that a 4.1.1 release is planned for > end of November, which isn't too far, but I was wondering if want to > have a stable release even earlier, right after the fixes for both > problems are in.
IMHO data corruption for our primary image format is an excellent reason to do a stable release at the soonest viable opportunity. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
