All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Peter Wu <peter@lekensteyn.nl>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 09/12] block/dmg: use SectorNumber from BLKX header
Date: Wed, 07 Jan 2015 13:08:56 -0500	[thread overview]
Message-ID: <54AD7638.8020204@redhat.com> (raw)
In-Reply-To: <1420566495-13284-10-git-send-email-peter@lekensteyn.nl>



On 01/06/2015 12:48 PM, Peter Wu wrote:
> Previously the sector table parsing relied on the previous offset of
> the DMG file. Now it uses the sector number from the BLKX header
> (see http://newosxbook.com/DMG.html).
>
> The implementation of dmg2img (from vu1tur) does not base the output
> sector on the location of the terminator (0xffffffff) either so it
> should be safe to drop this dependency on the previous state.
>
> (It makes somehow makes sense, a terminator should halt further
> processing of a block and is perhaps used to preallocate some space.)
>
> Signed-off-by: Peter Wu <peter@lekensteyn.nl>
> ---
>   v2: initial patch after suggestions from John Snow to read and use
>       these fields.
> ---
>   block/dmg.c | 12 +++++-------
>   1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/block/dmg.c b/block/dmg.c
> index 130efac..57922c5 100644
> --- a/block/dmg.c
> +++ b/block/dmg.c
> @@ -189,7 +189,6 @@ typedef struct DmgHeaderState {
>       /* used internally by dmg_read_mish_block to remember offsets of blocks
>        * across calls */
>       uint64_t data_fork_offset;
> -    uint64_t last_out_offset;
>       /* exported for dmg_open */
>       uint32_t max_compressed_size;
>       uint32_t max_sectors_per_chunk;
> @@ -205,6 +204,7 @@ static int dmg_read_mish_block(BDRVDMGState *s, DmgHeaderState *ds,
>       int64_t offset = 0;
>       uint64_t data_offset;
>       uint64_t in_offset = ds->data_fork_offset;
> +    uint64_t out_offset;
>
>       type = buff_read_uint32(buffer, offset);
>       /* skip data that is not a valid MISH block (invalid magic or too small) */
> @@ -213,6 +213,9 @@ static int dmg_read_mish_block(BDRVDMGState *s, DmgHeaderState *ds,
>           return 0;
>       }
>
> +    /* chunk offsets are relative to this sector number */
> +    out_offset = buff_read_uint64(buffer, offset + 8);
> +
>       /* location in data fork for (compressed) blob (in bytes) */
>       data_offset = buff_read_uint64(buffer, offset + 0x18);
>       in_offset += data_offset;
> @@ -233,10 +236,6 @@ static int dmg_read_mish_block(BDRVDMGState *s, DmgHeaderState *ds,
>           offset += 4;
>           if (s->types[i] != 0x80000005 && s->types[i] != 1 &&
>               s->types[i] != 2) {
> -            if (s->types[i] == 0xffffffff && i > 0) {
> -                ds->last_out_offset = s->sectors[i - 1] +
> -                                      s->sectorcounts[i - 1];
> -            }

This is exactly what I was hoping to see could be eliminated by reading 
the mish headers. Thanks for this.

>               chunk_count--;
>               i--;
>               offset += 36;
> @@ -245,7 +244,7 @@ static int dmg_read_mish_block(BDRVDMGState *s, DmgHeaderState *ds,
>           offset += 4;
>
>           s->sectors[i] = buff_read_uint64(buffer, offset);
> -        s->sectors[i] += ds->last_out_offset;
> +        s->sectors[i] += out_offset;
>           offset += 8;
>
>           s->sectorcounts[i] = buff_read_uint64(buffer, offset);
> @@ -419,7 +418,6 @@ static int dmg_open(BlockDriverState *bs, QDict *options, int flags,
>       s->offsets = s->lengths = s->sectors = s->sectorcounts = NULL;
>       /* used by dmg_read_mish_block to keep track of the current I/O position */
>       ds.data_fork_offset = 0;
> -    ds.last_out_offset = 0;
>       ds.max_compressed_size = 1;
>       ds.max_sectors_per_chunk = 1;
>
>

Much nicer.

Reviewed-by: John Snow <jsnow@redhat.com>

  reply	other threads:[~2015-01-07 18:09 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06 17:48 [Qemu-devel] [PATCH v2 00/12] block/dmg: (compatibility) fixes and bzip2 support Peter Wu
2015-01-06 17:48 ` [Qemu-devel] [PATCH v2 01/12] block/dmg: properly detect the UDIF trailer Peter Wu
2015-01-07 13:19   ` Stefan Hajnoczi
2015-01-07 14:19     ` Peter Wu
2015-01-14 16:17       ` Stefan Hajnoczi
2015-01-06 17:48 ` [Qemu-devel] [PATCH v2 02/12] block/dmg: extract mish block decoding functionality Peter Wu
2015-01-06 17:48 ` [Qemu-devel] [PATCH v2 03/12] block/dmg: extract processing of resource forks Peter Wu
2015-01-07 18:05   ` John Snow
2015-01-06 17:48 ` [Qemu-devel] [PATCH v2 04/12] block/dmg: process a buffer instead of reading ints Peter Wu
2015-01-06 17:48 ` [Qemu-devel] [PATCH v2 05/12] block/dmg: validate chunk size to avoid overflow Peter Wu
2015-01-07 18:05   ` John Snow
2015-01-06 17:48 ` [Qemu-devel] [PATCH v2 06/12] block/dmg: process XML plists Peter Wu
2015-01-07 18:06   ` John Snow
2015-01-06 17:48 ` [Qemu-devel] [PATCH v2 07/12] block/dmg: set virtual size to a non-zero value Peter Wu
2015-01-07 18:07   ` John Snow
2015-01-06 17:48 ` [Qemu-devel] [PATCH v2 08/12] block/dmg: fix sector data offset calculation Peter Wu
2015-01-07 18:08   ` John Snow
2015-01-06 17:48 ` [Qemu-devel] [PATCH v2 09/12] block/dmg: use SectorNumber from BLKX header Peter Wu
2015-01-07 18:08   ` John Snow [this message]
2015-01-06 17:48 ` [Qemu-devel] [PATCH v2 10/12] block/dmg: factor out block type check Peter Wu
2015-01-07 18:09   ` John Snow
2015-01-06 17:48 ` [Qemu-devel] [PATCH v2 11/12] block/dmg: support bzip2 block entry types Peter Wu
2015-01-07 11:08   ` Paolo Bonzini
2015-01-07 18:09   ` John Snow
2015-01-06 17:48 ` [Qemu-devel] [PATCH v2 12/12] block/dmg: improve zeroes handling Peter Wu
2015-01-07 18:10   ` John Snow
2015-01-14 16:16 ` [Qemu-devel] [PATCH v2 00/12] block/dmg: (compatibility) fixes and bzip2 support Stefan Hajnoczi

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=54AD7638.8020204@redhat.com \
    --to=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=peter@lekensteyn.nl \
    --cc=qemu-devel@nongnu.org \
    --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 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.