qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Jeff Cody <jcody@redhat.com>
Cc: kwolf@redhat.com, famz@redhat.com, qemu-devel@nongnu.org,
	stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v4 07/13] block: vhdx - log parsing, replay, and flush support
Date: Wed, 21 Aug 2013 17:09:30 +0200	[thread overview]
Message-ID: <20130821150930.GA18303@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <3480ba616f83aa60eeb31258cb4b56cd14f59c60.1376976937.git.jcody@redhat.com>

On Tue, Aug 20, 2013 at 02:01:18AM -0400, Jeff Cody wrote:

Will require more iterations of review, but here's what I have so far:

> +/* Returns true if the GUID is zero */
> +static bool vhdx_log_guid_is_zero(MSGUID *guid)
> +{
> +    int i;
> +    int ret = 0;
> +
> +    /* If either the log guid, or log length is zero,
> +     * then a replay log is not present */

The comment about log length here is not relevant to this function.

> +    for (i = 0; i < sizeof(MSGUID); i++) {
> +        ret |= ((uint8_t *) guid)[i];
> +    }
> +
> +    return ret == 0;
> +}

IMO there is no need for this function.  Just declare a const MSGUID
zero_guid = {0} global and use memcmp():

  is_zero = guid_eq(guid, zero_guid);

> +static bool vhdx_log_desc_is_valid(VHDXLogDescriptor *desc,
> +                                   VHDXLogEntryHeader *hdr)
> +{
> +    bool ret = false;
> +
> +    if (desc->sequence_number != hdr->sequence_number) {
> +        goto exit;
> +    }
> +    if (desc->file_offset % VHDX_LOG_SECTOR_SIZE) {
> +        goto exit;
> +    }
> +
> +    if (!memcmp(&desc->signature, "zero", 4)) {
> +        if (!desc->zero_length % VHDX_LOG_SECTOR_SIZE) {

Precedence looks wrong here, did you mean:

if (desc->zero_length % VHDX_LOG_SECTOR_SIZE == 0) {

> +static int vhdx_log_search(BlockDriverState *bs, BDRVVHDXState *s,
> +                           VHDXLogSequence *logs)
> +{
> +    int ret = 0;
> +
> +    uint64_t curr_seq = 0;
> +    VHDXLogSequence candidate = { 0 };
> +    VHDXLogSequence current = { 0 };
> +
> +    uint32_t tail;
> +    bool seq_valid = false;
> +    VHDXLogEntryHeader hdr = { 0 };
> +    VHDXLogEntries curr_log;
> +
> +    memcpy(&curr_log, &s->log, sizeof(VHDXLogEntries));
> +    curr_log.write = curr_log.length;   /* assume log is full */
> +    curr_log.read = 0;
> +
> +
> +    /* now we will go through the whole log sector by sector, until
> +     * we find a valid, active log sequence, or reach the end of the
> +     * log buffer */
> +    for (;;) {
> +        tail = curr_log.read;
> +
> +        curr_seq = 0;
> +        memset(&current, 0, sizeof(current));

You could declare curr_seq, current, and friends inside the for loop
scope to avoid duplicate initializations.

> +int vhdx_parse_log(BlockDriverState *bs, BDRVVHDXState *s)
> +{
> +    int ret = 0;
> +    VHDXHeader *hdr;
> +    VHDXLogSequence logs = { 0 };
> +
> +    hdr = s->headers[s->curr_header];
> +
> +    /* s->log.hdr is freed in vhdx_close() */

vhdx_close() is not called when .bdrv_open() fails so s->log.hdr is
leaked.

> +    if (s->log.hdr == NULL) {
> +        s->log.hdr = qemu_blockalign(bs, sizeof(VHDXLogEntryHeader));
> +    }
> +
> +    s->log.offset = hdr->log_offset;
> +    s->log.length = hdr->log_length;
> +
> +    if (s->log.offset < VHDX_LOG_MIN_SIZE ||
> +        s->log.offset % VHDX_LOG_MIN_SIZE) {
> +        ret = -EINVAL;
> +        goto exit;
> +    }

To be completely safe we should probably ensure that the log does not
overlap any other structures, as mentioned in the spec.

  reply	other threads:[~2013-08-21 15:09 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20  6:01 [Qemu-devel] [PATCH v4 00/13] VHDX log replay and write support, .bdrv_create() Jeff Cody
2013-08-20  6:01 ` [Qemu-devel] [PATCH v4 01/13] block: vhdx - minor comments and typo correction Jeff Cody
2013-08-20  6:01 ` [Qemu-devel] [PATCH v4 02/13] block: vhdx - add header update capability Jeff Cody
2013-08-20  6:01 ` [Qemu-devel] [PATCH v4 03/13] block: vhdx code movement - VHDXMetadataEntries and BDRVVHDXState to header Jeff Cody
2013-08-20  6:01 ` [Qemu-devel] [PATCH v4 04/13] block: vhdx - log support struct and defines Jeff Cody
2013-08-20  6:01 ` [Qemu-devel] [PATCH v4 05/13] block: vhdx - break endian translation functions out Jeff Cody
2013-08-20  6:01 ` [Qemu-devel] [PATCH v4 06/13] block: vhdx - update log guid in header, and first write tracker Jeff Cody
2013-08-20  6:01 ` [Qemu-devel] [PATCH v4 07/13] block: vhdx - log parsing, replay, and flush support Jeff Cody
2013-08-21 15:09   ` Stefan Hajnoczi [this message]
2013-08-21 15:38     ` Jeff Cody
2013-08-20  6:01 ` [Qemu-devel] [PATCH v4 08/13] block: vhdx - add log write support Jeff Cody
2013-08-20  6:01 ` [Qemu-devel] [PATCH v4 09/13] block: vhdx " Jeff Cody
2013-08-20  6:01 ` [Qemu-devel] [PATCH v4 10/13] block: vhdx - move more endian translations to vhdx-endian.c Jeff Cody
2013-08-20  6:01 ` [Qemu-devel] [PATCH v4 11/13] block: vhdx - break out code operations to functions Jeff Cody
2013-08-20  6:01 ` [Qemu-devel] [PATCH v4 12/13] block: vhdx - fix comment typos in header, fix incorrect struct fields Jeff Cody
2013-08-20  6:01 ` [Qemu-devel] [PATCH v4 13/13] block: vhdx - add .bdrv_create() support Jeff Cody
2013-08-20 14:26 ` [Qemu-devel] [PATCH v4 00/13] VHDX log replay and write support, .bdrv_create() Kevin Wolf

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=20130821150930.GA18303@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --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 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).