From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, dplotnikov@virtuozzo.com,
vsementsov@virtuozzo.com, qemu-block@nongnu.org,
mreitz@redhat.com
Subject: [PATCH] qcow2: Explicit mention of padding bytes
Date: Thu, 27 Feb 2020 08:45:08 -0600 [thread overview]
Message-ID: <20200227144508.1078501-1-eblake@redhat.com> (raw)
Although we already covered the need for padding bytes with our
changes in commit 3ae3fcfa, commit 66fcbca5 just added one byte and
relied on the earlier text for implicitly covering 7 padding bytes.
For consistency with other parts of the header, it does not hurt to be
explicit that this version of the header is using padding bytes, and
if we later add other extension fields, we can rework the allocation
of those padding bytes to match those additions.
Signed-off-by: Eric Blake <eblake@redhat.com>
---
docs/interop/qcow2.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/docs/interop/qcow2.txt b/docs/interop/qcow2.txt
index 5597e244746e..193ac7c5c1af 100644
--- a/docs/interop/qcow2.txt
+++ b/docs/interop/qcow2.txt
@@ -209,6 +209,8 @@ version 2.
Available compression type values:
0: zlib <https://www.zlib.net/>
+ 105 - m: Zero padding to round up the header size to the next
+ multiple of 8.
=== Header padding ===
--
2.25.1
next reply other threads:[~2020-02-27 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 14:45 Eric Blake [this message]
2020-02-27 14:54 ` [PATCH] qcow2: Explicit mention of padding bytes Max Reitz
2020-02-27 14:57 ` Vladimir Sementsov-Ogievskiy
-- strict thread matches above, loose matches on Subject: below --
2023-05-22 18:46 Eric Blake
2023-05-22 20:26 ` Vladimir Sementsov-Ogievskiy
2023-06-01 21:25 ` Eric Blake
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=20200227144508.1078501-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=dplotnikov@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).