From: David Gibson <david@gibson.dropbear.id.au>
To: Daniel Henrique Barboza <danielhb413@gmail.com>
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org, clg@kaod.org
Subject: Re: [PATCH v2 1/4] target/ppc: initialize 'val' union in kvm_get_one_spr()
Date: Thu, 31 Mar 2022 12:20:22 +1100 [thread overview]
Message-ID: <YkUB1miNaGYsEgy1@yekko> (raw)
In-Reply-To: <20220331001717.616938-2-danielhb413@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2649 bytes --]
On Wed, Mar 30, 2022 at 09:17:14PM -0300, Daniel Henrique Barboza wrote:
> Valgrind isn't convinced that we are initializing the values we assign
> to env->spr[spr] because it doesn't understand that the 'val' union is
> being written by the kvm_vcpu_ioctl() that follows (via struct
> kvm_one_reg).
>
> This results in Valgrind complaining about uninitialized values every
> time we use env->spr in a conditional, like this instance:
>
> ==707578== Thread 1:
> ==707578== Conditional jump or move depends on uninitialised value(s)
> ==707578== at 0xA10A40: hreg_compute_hflags_value (helper_regs.c:106)
> ==707578== by 0xA10C9F: hreg_compute_hflags (helper_regs.c:173)
> ==707578== by 0xA110F7: hreg_store_msr (helper_regs.c:262)
> ==707578== by 0xA051A3: ppc_cpu_reset (cpu_init.c:7168)
> ==707578== by 0xD4730F: device_transitional_reset (qdev.c:799)
> ==707578== by 0xD4A11B: resettable_phase_hold (resettable.c:182)
> ==707578== by 0xD49A77: resettable_assert_reset (resettable.c:60)
> ==707578== by 0xD4994B: resettable_reset (resettable.c:45)
> ==707578== by 0xD458BB: device_cold_reset (qdev.c:296)
> ==707578== by 0x48FBC7: cpu_reset (cpu-common.c:114)
> ==707578== by 0x97B5EB: spapr_reset_vcpu (spapr_cpu_core.c:38)
> ==707578== by 0x97BABB: spapr_cpu_core_reset (spapr_cpu_core.c:209)
> ==707578== Uninitialised value was created by a stack allocation
> ==707578== at 0xB11F08: kvm_get_one_spr (kvm.c:543)
>
> Initializing 'val' has no impact in the logic and makes Valgrind output
> more bearable.
>
> Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> target/ppc/kvm.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/target/ppc/kvm.c b/target/ppc/kvm.c
> index dc93b99189..858866ecd4 100644
> --- a/target/ppc/kvm.c
> +++ b/target/ppc/kvm.c
> @@ -543,10 +543,11 @@ static void kvm_get_one_spr(CPUState *cs, uint64_t id, int spr)
> {
> PowerPCCPU *cpu = POWERPC_CPU(cs);
> CPUPPCState *env = &cpu->env;
> + /* Init 'val' to avoid "uninitialised value" Valgrind warnings */
> union {
> uint32_t u32;
> uint64_t u64;
> - } val;
> + } val = { };
> struct kvm_one_reg reg = {
> .id = id,
> .addr = (uintptr_t) &val,
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-03-31 1:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 0:17 [PATCH v2 0/4] ppc: valgrind "uninitialized values" fixes Daniel Henrique Barboza
2022-03-31 0:17 ` [PATCH v2 1/4] target/ppc: initialize 'val' union in kvm_get_one_spr() Daniel Henrique Barboza
2022-03-31 1:20 ` David Gibson [this message]
2022-03-31 0:17 ` [PATCH v2 2/4] target/ppc: init 'lpcr' in kvmppc_enable_cap_large_decr() Daniel Henrique Barboza
2022-03-31 1:25 ` David Gibson
2022-03-31 17:17 ` Daniel Henrique Barboza
2022-03-31 17:36 ` Richard Henderson
2022-03-31 18:46 ` Daniel Henrique Barboza
2022-04-01 3:40 ` David Gibson
2022-04-05 19:37 ` Daniel Henrique Barboza
2022-04-01 3:38 ` David Gibson
2022-03-31 0:17 ` [PATCH v2 3/4] target/ppc: init 'sregs' in kvmppc_put_books_sregs() Daniel Henrique Barboza
2022-03-31 0:17 ` [PATCH v2 4/4] target/ppc: init 'rmmu_info' in kvm_get_radix_page_info() Daniel Henrique Barboza
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=YkUB1miNaGYsEgy1@yekko \
--to=david@gibson.dropbear.id.au \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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.