From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, shhuiw@163.com
Subject: Re: [Qemu-devel] [PATCH] cow: make padding in the header explicit
Date: Thu, 04 Sep 2014 06:07:32 -0600 [thread overview]
Message-ID: <54085604.2050005@redhat.com> (raw)
In-Reply-To: <1409821121-20645-1-git-send-email-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
On 09/04/2014 02:58 AM, Stefan Hajnoczi wrote:
> On-disk structures should be marked packed so the compiler does not
> insert padding for field alignment. Padding should be explicit so
> on-disk layout is obvious and we don't rely on the architecture-specific
> ABI for alignment rules.
>
> The pahole(1) diff shows that the padding is now explicit and offsets
> are unchanged:
>
> char backing_file[1024]; /* 8 1024 */
> /* --- cacheline 16 boundary (1024 bytes) was 8 bytes ago --- */
> int32_t mtime; /* 1032 4 */
> -
> - /* XXX 4 bytes hole, try to pack */
> -
> + uint32_t padding; /* 1036 4 */
> uint64_t size; /* 1040 8 */
Was a 32-bit build also inserting this padding, or do we have historical
differences where 32-bit and 64-bit cow files are actually different,
and we may need to be prepared to parse files from both sources?
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
next prev parent reply other threads:[~2014-09-04 12:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 8:58 [Qemu-devel] [PATCH] cow: make padding in the header explicit Stefan Hajnoczi
2014-09-04 9:26 ` Kevin Wolf
2014-09-04 9:47 ` Benoît Canet
2014-09-04 12:07 ` Eric Blake [this message]
2014-09-04 12:57 ` shhuiw
2014-09-04 13:51 ` Stefan Hajnoczi
2014-09-04 14:10 ` Kevin Wolf
2014-09-04 15:43 ` Stefan Hajnoczi
2014-09-05 9:13 ` Kevin Wolf
2014-09-05 11:01 ` Markus Armbruster
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=54085604.2050005@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shhuiw@163.com \
--cc=stefanha@redhat.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).