From: Paolo Bonzini <pbonzini@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-trivial <qemu-trivial@nongnu.org>,
Stefan Weil <sw@weilnetz.de>, Kevin Wolf <kwolf@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] block: Fix compiler warning (-Werror=uninitialized)
Date: Thu, 19 Sep 2013 19:22:34 +0200 [thread overview]
Message-ID: <523B32DA.3020007@redhat.com> (raw)
In-Reply-To: <523B2D6B.9050601@suse.de>
Il 19/09/2013 18:59, Andreas Färber ha scritto:
> Am 17.09.2013 18:43, schrieb Stefan Weil:
>> The patch fixes a warning from gcc (Debian 4.6.3-14+rpi1) 4.6.3:
>>
>> block/stream.c:141:22: error:
>> ‘copy’ may be used uninitialized in this function [-Werror=uninitialized]
>>
>> This is not a real bug - a better compiler would not complain.
>>
>> Now 'copy' has always a defined value, so the check for ret >= 0
>> can be removed.
>>
>> Signed-off-by: Stefan Weil <sw@weilnetz.de>
>> ---
>> block/stream.c | 5 ++---
>> 1 file changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/block/stream.c b/block/stream.c
>> index 078ce4a..fc19194 100644
>> --- a/block/stream.c
>> +++ b/block/stream.c
>> @@ -108,7 +108,7 @@ static void coroutine_fn stream_run(void *opaque)
>>
>> for (sector_num = 0; sector_num < end; sector_num += n) {
>> uint64_t delay_ns = 0;
>> - bool copy;
>> + bool copy = false;
>>
>> wait:
>> /* Note that even when no rate limit is applied we need to yield
>> @@ -123,7 +123,6 @@ wait:
>> STREAM_BUFFER_SIZE / BDRV_SECTOR_SIZE, &n);
>> if (ret == 1) {
>> /* Allocated in the top, no need to copy. */
>> - copy = false;
>> } else if (ret >= 0) {
>> /* Copy if allocated in the intermediate images. Limit to the
>> * known-unallocated area [sector_num, sector_num+n). */
>
> Sorry for not spotting this patch earlier. This hunk looks wrong and
> needs to be dropped, I believe. In the ret >= 0 && copy case, there is a
> "goto wait" which would now no longer be able to go from copy == true ->
> copy == false. Not sure if that can happen in practice.
Yes, if the guest writes to the area that the job is copying. It
wouldn't cause any data corruption, only do useless work on those
sectors. A better patch would thus remove the initializer and move the
"copy = false" before "if (ret == 1)".
Paolo
> Andreas
>
>> @@ -138,7 +137,7 @@ wait:
>> copy = (ret == 1);
>> }
>> trace_stream_one_iteration(s, sector_num, n, ret);
>> - if (ret >= 0 && copy) {
>> + if (copy) {
>> if (s->common.speed) {
>> delay_ns = ratelimit_calculate_delay(&s->limit, n);
>> if (delay_ns > 0) {
>>
>
>
next prev parent reply other threads:[~2013-09-19 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 16:43 [Qemu-devel] [PATCH] block: Fix compiler warning (-Werror=uninitialized) Stefan Weil
2013-09-19 14:44 ` Stefan Hajnoczi
2013-09-19 16:59 ` Andreas Färber
2013-09-19 17:22 ` Paolo Bonzini [this message]
2013-09-20 10:42 ` 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=523B32DA.3020007@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@redhat.com \
--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 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).