From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: qemu-devel@nongnu.org
Cc: Daniel Henrique Barboza <danielhb413@gmail.com>,
qemu-ppc@nongnu.org, clg@kaod.org, david@gibson.dropbear.id.au
Subject: [PATCH 1/2] ppc/pnv: initialize 'taddr' in pnv_phb3_translate_tve()
Date: Wed, 26 Jan 2022 10:41:36 -0300 [thread overview]
Message-ID: <20220126134137.791968-2-danielhb413@gmail.com> (raw)
In-Reply-To: <20220126134137.791968-1-danielhb413@gmail.com>
The 'taddr' variable is left unintialized, being set only inside the
"while ((lev--) >= 0)" loop where we get the TCE address. The 'lev' var
is an int32_t that is being initiliazed by the GETFIELD() macro, which
returns an uint64_t.
For a human reader this means that 'lev' will always be positive or zero.
But some compilers may beg to differ. 'lev' being an int32_t can in theory
be set as negative, and the "while ((lev--) >= 0)" loop might never be
reached, and 'taddr' will be left unitialized. This can cause phb3_error()
to use 'taddr' uninitialized down below:
if ((is_write & !(tce & 2)) || ((!is_write) && !(tce & 1))) {
phb3_error(phb, "TCE access fault at 0x%"PRIx64, taddr);
Setting 'taddr' to the top level base address will make compilers happy.
Resolves: https://gitlab.com/qemu-project/qemu/-/issues/573
Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
---
hw/pci-host/pnv_phb3.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/hw/pci-host/pnv_phb3.c b/hw/pci-host/pnv_phb3.c
index 7fb35dc031..617d42c5a0 100644
--- a/hw/pci-host/pnv_phb3.c
+++ b/hw/pci-host/pnv_phb3.c
@@ -788,6 +788,17 @@ static void pnv_phb3_translate_tve(PnvPhb3DMASpace *ds, hwaddr addr,
/* Top level table base address */
base = tta << 12;
+ /*
+ * Some compilers will complain that the "TCE access fault"
+ * phb3_error() down below will use 'taddr' uninitialized
+ * because, in theory, the loop that sets 'taddr' is skippable
+ * due to 'lev' being an signed int.
+ *
+ * Setting 'taddr 'to the base address will bring piece of mind
+ * to such compilers.
+ */
+ taddr = base;
+
/* Total shift to first level */
sh = tbl_shift * lev + tce_shift;
--
2.34.1
next prev parent reply other threads:[~2022-01-26 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 13:41 [PATCH 0/2] initialize 'taddr' in pnv_phbX_translate_tve() Daniel Henrique Barboza
2022-01-26 13:41 ` Daniel Henrique Barboza [this message]
2022-01-26 17:28 ` [PATCH 1/2] ppc/pnv: initialize 'taddr' in pnv_phb3_translate_tve() Matheus K. Ferst
2022-01-26 20:09 ` Daniel Henrique Barboza
2022-01-26 13:41 ` [PATCH 2/2] ppc/pnv: initialize 'taddr' in pnv_phb4_translate_tve() 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=20220126134137.791968-2-danielhb413@gmail.com \
--to=danielhb413@gmail.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--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 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).