From: Aurelien Jarno <aurelien@aurel32.net>
To: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [PATCH] qemu: avoid returning uninitialized value in apic_mem_readl
Date: Mon, 07 Apr 2008 11:12:26 +0200 [thread overview]
Message-ID: <47F9E57A.9080906@aurel32.net> (raw)
In-Reply-To: <20080406233344.GC7213@tapir>
Carlo Marcelo Arenas Belon a écrit :
> complement 64173d009c1f4d163c425b14aa650df5b982428a to avoid :
>
> kvm-65/qemu/hw/apic.c: In function `apic_mem_readl':
> kvm-65/qemu/hw/apic.c:592: warning: 'val' might be used uninitialized in this function
>
> Signed-off-by: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
> ---
> qemu/hw/apic.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/qemu/hw/apic.c b/qemu/hw/apic.c
> index 4102493..b69ad75 100644
> --- a/qemu/hw/apic.c
> +++ b/qemu/hw/apic.c
> @@ -616,6 +616,7 @@ static uint32_t apic_mem_readl(void *opaque, target_phys_addr_t addr)
> val = apic_get_ppr(s);
> break;
> case 0x0b:
> + val = 0;
> break;
> case 0x0d:
> val = s->log_dest << 24;
The equivalent of commit 64173d009c1f4d163c425b14aa650df5b982428a in
qemu has been done this way. So a merge of qemu SVN should fix this problem.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
prev parent reply other threads:[~2008-04-07 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-06 23:33 [PATCH] qemu: avoid returning uninitialized value in apic_mem_readl Carlo Marcelo Arenas Belon
2008-04-07 9:12 ` Aurelien Jarno [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=47F9E57A.9080906@aurel32.net \
--to=aurelien@aurel32.net \
--cc=carenas@sajinet.com.pe \
--cc=kvm-devel@lists.sourceforge.net \
/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