All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	gollub@b1-systems.de, Alexander Graf <agraf@suse.de>,
	lcapitulino@redhat.com
Subject: Re: [Qemu-devel] VDI patches
Date: Mon, 19 Mar 2012 12:46:39 +0100	[thread overview]
Message-ID: <4F671C9F.90100@redhat.com> (raw)
In-Reply-To: <4F643902.7080705@weilnetz.de>

Am 17.03.2012 08:10, schrieb Stefan Weil:
> Am 17.03.2012 04:11, schrieb qemu@buildbot.b1-systems.de:
>> The Buildbot has detected a new failure on builder 
>> block_i386_debian_6_0 while building qemu.
>> Full details are available at:
>> http://buildbot.b1-systems.de/qemu/builders/block_i386_debian_6_0/builds/215
>>
>> Buildbot URL: http://buildbot.b1-systems.de/qemu/
>>
>> Buildslave for this Build: yuzuki
>>
>> Build Reason: The Nightly scheduler named 'nightly_block' triggered 
>> this build
>> Build Source Stamp: [branch block] HEAD
>> Blamelist:
>>
>> BUILD FAILED: failed compile
>>
>> sincerely,
>> -The Buildbot
> 
> Hi Kevin, hi Paolo,
> 
> the build failure is caused by the vdi changes: some versions of gcc
> detect uninitialized local variables (my gcc 4.4.5 does not).
> 
> I don't think that it's really an error because the code is guarded
> by the local variable 'block', but not all compilers are clever enough,
> so it should be fixed.
> 
> It can be fixed by modifying commit af93911fd45f4de34ca2d5813905e2cf43675c98
> (vdi: move aiocb fields to locals) like that:
> 
> --- a/block/vdi.c
> +++ b/block/vdi.c
> @@ -519,8 +519,8 @@ static int vdi_co_write(BlockDriverState *bs,
>       uint32_t block_index;
>       uint32_t sector_in_block;
>       uint32_t n_sectors;
> -    uint32_t bmap_first;
> -    uint32_t bmap_last;
> +    uint32_t bmap_first = VDI_UNALLOCATED;
> +    uint32_t bmap_last = VDI_UNALLOCATED;
>       uint8_t *block = NULL;
>       int ret = 0;

Paolo, can you send a v2?

Kevin

      parent reply	other threads:[~2012-03-19 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-17  3:11 [Qemu-devel] buildbot failure in qemu on block_i386_debian_6_0 qemu
2012-03-17  7:10 ` [Qemu-devel] VDI patches (was: buildbot failure in qemu on block_i386_debian_6_0) Stefan Weil
2012-03-17  7:33   ` [Qemu-devel] VDI patches Paolo Bonzini
2012-03-19 11:46   ` Kevin Wolf [this message]

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=4F671C9F.90100@redhat.com \
    --to=kwolf@redhat.com \
    --cc=agraf@suse.de \
    --cc=gollub@b1-systems.de \
    --cc=lcapitulino@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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.