All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: peter.maydell@linaro.org, mreitz@redhat.com,
	mdroth@linux.vnet.ibm.com, qemu-block@nongnu.org,
	qemu-devel@nongnu.org
Subject: Re: Early 4.1.1 release for image corruption fixes?
Date: Fri, 25 Oct 2019 16:03:19 +0100	[thread overview]
Message-ID: <20191025150319.GD3581@redhat.com> (raw)
In-Reply-To: <20191025142915.GG7275@localhost.localdomain>

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 :|



      parent reply	other threads:[~2019-10-25 15:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-25 14:29 Early 4.1.1 release for image corruption fixes? Kevin Wolf
2019-10-25 14:31 ` Max Reitz
2019-10-25 15:03 ` Daniel P. Berrangé [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191025150319.GD3581@redhat.com \
    --to=berrange@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=mreitz@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.