qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: "Matheus K. Ferst" <matheus.ferst@eldorado.org.br>,
	qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, clg@kaod.org, david@gibson.dropbear.id.au
Subject: Re: [PATCH v2 1/2] ppc/pnv: use a do-while() loop in pnv_phb3_translate_tve()
Date: Thu, 27 Jan 2022 09:09:10 -0300	[thread overview]
Message-ID: <171f02a2-cf95-fd79-4dc7-94a667f3ef81@gmail.com> (raw)
In-Reply-To: <5b9fc0c6-f6b4-64e1-9126-de54229d05c1@eldorado.org.br>



On 1/27/22 08:41, Matheus K. Ferst wrote:
> On 26/01/2022 17:14, Daniel Henrique Barboza wrote:
>> 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);
>>
>> A quick way of fixing it is to use a do/while() loop. This will keep the
>> same semanting as the existing while() loop does and the compiler will
>> understand that 'taddr' will be initialized at least once.
>>
>> Suggested-by: Matheus K. Ferst <matheus.ferst@eldorado.org.br>
>> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/573
>> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com>
>> ---
>>   hw/pci-host/pnv_phb3.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/pci-host/pnv_phb3.c b/hw/pci-host/pnv_phb3.c
>> index 7fb35dc031..39a6184419 100644
>> --- a/hw/pci-host/pnv_phb3.c
>> +++ b/hw/pci-host/pnv_phb3.c
>> @@ -792,7 +792,7 @@ static void pnv_phb3_translate_tve(PnvPhb3DMASpace *ds, hwaddr addr,
>>           sh = tbl_shift * lev + tce_shift;
>>
>>           /* TODO: Multi-level untested */
>> -        while ((lev--) >= 0) {
>> +        do {
>>               /* Grab the TCE address */
>>               taddr = base | (((addr >> sh) & ((1ul << tbl_shift) - 1)) << 3);
>>               if (dma_memory_read(&address_space_memory, taddr, &tce,
>> @@ -813,7 +813,7 @@ static void pnv_phb3_translate_tve(PnvPhb3DMASpace *ds, hwaddr addr,
>>               }
>>               sh -= tbl_shift;
>>               base = tce & ~0xfffull;
>> -        }
>> +        } while ((lev--) >= 0);
> 
> This changes the number of iterations in this loop.

ooofff

> We'd need "while ((--lev) >= 0)" to keep it the same, but then we would be checking "!(tce & 3)" for the last iteration. Is that a problem?


I don't think that's a problem because then (lev >= 0) will not be true and we'll
not going to check !(tce &3), so even if 'tce' has a bogus value it's fine.


Daniel






> 
> Thanks,
> Matheus K. Ferst
> Instituto de Pesquisas ELDORADO <http://www.eldorado.org.br/>
> Analista de Software
> Aviso Legal - Disclaimer <https://www.eldorado.org.br/disclaimer.html>


  reply	other threads:[~2022-01-27 12:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 20:14 [PATCH v2 0/2] use a do-while() loop in pnv_phbX_translate_tve() Daniel Henrique Barboza
2022-01-26 20:14 ` [PATCH v2 1/2] ppc/pnv: use a do-while() loop in pnv_phb3_translate_tve() Daniel Henrique Barboza
2022-01-27 11:41   ` Matheus K. Ferst
2022-01-27 12:09     ` Daniel Henrique Barboza [this message]
2022-01-27 12:28       ` Matheus K. Ferst
2022-01-27 12:35         ` Daniel Henrique Barboza
2022-01-27 12:32       ` BALATON Zoltan
2022-01-26 20:14 ` [PATCH v2 2/2] ppc/pnv: use a do-while() loop in pnv_phb4_translate_tve() Daniel Henrique Barboza
2022-01-27 11:41   ` Matheus K. Ferst
2022-01-27 11:49     ` 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=171f02a2-cf95-fd79-4dc7-94a667f3ef81@gmail.com \
    --to=danielhb413@gmail.com \
    --cc=clg@kaod.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=matheus.ferst@eldorado.org.br \
    --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).