qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	qemu-devel@nongnu.org,
	Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [PATCH for 6.0 v2] hw/intc/i8259: Refactor pic_read_irq() to avoid uninitialized variable
Date: Thu, 18 Mar 2021 17:28:23 +0100	[thread overview]
Message-ID: <99adc22b-295c-b68c-8aef-940baa88a372@redhat.com> (raw)
In-Reply-To: <e71d95de-a1ce-a8e5-78e-1751210329e@eik.bme.hu>

On 3/18/21 5:24 PM, BALATON Zoltan wrote:
> On Thu, 18 Mar 2021, Philippe Mathieu-Daudé wrote:
>> Some compiler versions are smart enough to detect a potentially
>> uninitialized variable, but are not smart enough to detect that this
>> cannot happen due to the code flow:
>>
>> ../hw/intc/i8259.c: In function ‘pic_read_irq’:
>> ../hw/intc/i8259.c:203:13: error: ‘irq2’ may be used uninitialized in
>> this function [-Werror=maybe-uninitialized]
>>   203 |         irq = irq2 + 8;
>>       |         ~~~~^~~~~~~~~~
>>
>> Restrict irq2 variable use to the inner statement.
>>
>> Fixes: 78ef2b6989f ("i8259: Reorder intack in pic_read_irq")
>> Reported-by: Christian Borntraeger <borntraeger@de.ibm.com>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>> ---
>> Supersedes: <20210318154738.27094-1-borntraeger@de.ibm.com>
>> ---
>> hw/intc/i8259.c | 11 ++++++-----
>> 1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/hw/intc/i8259.c b/hw/intc/i8259.c
>> index 344fd04db14..52c039c6c03 100644
>> --- a/hw/intc/i8259.c
>> +++ b/hw/intc/i8259.c
>> @@ -176,10 +176,12 @@ static void pic_intack(PICCommonState *s, int irq)
>> int pic_read_irq(DeviceState *d)
>> {
>>     PICCommonState *s = PIC_COMMON(d);
>> -    int irq, irq2, intno;
>> +    int irq, intno;
>>
>>     irq = pic_get_irq(s);
>>     if (irq >= 0) {
>> +        int irq2;
>> +
>>         if (irq == 2) {
>>             irq2 = pic_get_irq(slave_pic);
>>             if (irq2 >= 0) {
>> @@ -189,8 +191,11 @@ int pic_read_irq(DeviceState *d)
>>                 irq2 = 7;
>>             }
>>             intno = slave_pic->irq_base + irq2;
>> +            pic_intack(s, irq);
>> +            irq = irq2 + 8;
>>         } else {
>>             intno = s->irq_base + irq;
>> +            pic_intack(s, irq);
>>         }
>>         pic_intack(s, irq);
> 
> Do you still need this pic_intack() here or did you intend to move it in
> the if above?

I forgot to remove it indeed, thanks!

>>     } else {
>> @@ -199,10 +204,6 @@ int pic_read_irq(DeviceState *d)
>>         intno = s->irq_base + irq;
>>     }
>>
>> -    if (irq == 2) {
>> -        irq = irq2 + 8;
>> -    }
>> -
>> #ifdef DEBUG_IRQ_LATENCY
>>     printf("IRQ%d latency=%0.3fus\n",
>>            irq,
>>



  reply	other threads:[~2021-03-18 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 16:09 [PATCH for 6.0 v2] hw/intc/i8259: Refactor pic_read_irq() to avoid uninitialized variable Philippe Mathieu-Daudé
2021-03-18 16:24 ` BALATON Zoltan
2021-03-18 16:28   ` Philippe Mathieu-Daudé [this message]
2021-03-18 22:50 ` Richard Henderson

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=99adc22b-295c-b68c-8aef-940baa88a372@redhat.com \
    --to=philmd@redhat.com \
    --cc=balaton@eik.bme.hu \
    --cc=borntraeger@de.ibm.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@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).