From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-block@nongnu.org, mreitz@redhat.com
Subject: [PATCH for-5.0 v2 0/4] bug fixes extracted from larger qcow2 zero bit work
Date: Tue, 24 Mar 2020 12:42:29 -0500 [thread overview]
Message-ID: <20200324174233.1622067-1-eblake@redhat.com> (raw)
My proposal [1] to add an autoclear all-zero-content bit to the qcow2
format has now stalled into 5.1 territory, but several patches in my
initial proposal are uncontroversial and obvious bug fixes worth
having in 5.0.
[1] https://lists.gnu.org/archive/html/qemu-devel/2020-01/msg08075.html
Eric Blake (4):
qcow2: Comment typo fixes
qcow2: List autoclear bit names in header
qcow2: Avoid feature name extension on small cluster size
sheepdog: Consistently set bdrv_has_zero_init_truncate
docs/interop/qcow2.txt | 3 ++-
block/qcow2.c | 29 +++++++++++++++++++++++------
block/sheepdog.c | 2 ++
tests/qemu-iotests/031.out | 8 ++++----
tests/qemu-iotests/036 | 6 ++++--
tests/qemu-iotests/036.out | 4 ++--
tests/qemu-iotests/061 | 6 ++++--
tests/qemu-iotests/061.out | 14 +++++++-------
8 files changed, 48 insertions(+), 24 deletions(-)
--
2.26.0.rc2
next reply other threads:[~2020-03-24 17:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 17:42 Eric Blake [this message]
2020-03-24 17:42 ` [PATCH v2 1/4] qcow2: Comment typo fixes Eric Blake
2020-03-24 17:42 ` [PATCH v2 2/4] qcow2: List autoclear bit names in header Eric Blake
2020-03-24 17:42 ` [PATCH v2 3/4] qcow2: Avoid feature name extension on small cluster size Eric Blake
2020-03-25 12:42 ` Max Reitz
2020-03-25 13:18 ` Eric Blake
2020-03-25 13:52 ` Max Reitz
2020-03-25 14:01 ` Eric Blake
2020-03-24 17:42 ` [PATCH v2 4/4] sheepdog: Consistently set bdrv_has_zero_init_truncate Eric Blake
2020-03-24 19:33 ` John Snow
2020-03-25 14:45 ` [PATCH-for-5.0 " Philippe Mathieu-Daudé
2020-03-26 13:32 ` [PATCH for-5.0 v2 0/4] bug fixes extracted from larger qcow2 zero bit work Max Reitz
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=20200324174233.1622067-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--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).