From: Kevin Wolf <kwolf@redhat.com>
To: mdroth@linux.vnet.ibm.com
Cc: kwolf@redhat.com, peter.maydell@linaro.org,
qemu-devel@nongnu.org, qemu-block@nongnu.org, mreitz@redhat.com
Subject: Early 4.1.1 release for image corruption fixes?
Date: Fri, 25 Oct 2019 16:29:15 +0200 [thread overview]
Message-ID: <20191025142915.GG7275@localhost.localdomain> (raw)
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.
Peter, if we haven't made a decision until then, maybe discussing this
is an agenda item for QEMU Summit, too.
Kevin
next reply other threads:[~2019-10-25 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 14:29 Kevin Wolf [this message]
2019-10-25 14:31 ` Early 4.1.1 release for image corruption fixes? Max Reitz
2019-10-25 15:03 ` Daniel P. Berrangé
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=20191025142915.GG7275@localhost.localdomain \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).