From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Subject: Re: [PATCH] hw/intc/openpic: Avoid taking address of out-of-bounds array index
Date: Wed, 6 Nov 2024 09:45:12 +0000 [thread overview]
Message-ID: <83926eb8-c5d7-4edf-b180-cc20c95a4c04@linaro.org> (raw)
In-Reply-To: <20241105180205.3074071-1-peter.maydell@linaro.org>
On 11/5/24 18:02, Peter Maydell wrote:
> The clang sanitizer complains about the code in the EOI handling
> of openpic_cpu_write_internal():
>
> UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1 ./build/clang/qemu-system-ppc -M mac99,graphics=off -display none -kernel day15/invaders.elf
> ../../hw/intc/openpic.c:1034:16: runtime error: index -1 out of bounds for type 'IRQSource[264]' (aka 'struct IRQSource[264]')
> SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../../hw/intc/openpic.c:1034:16 in
>
> This is because we do
> src = &opp->src[n_IRQ];$
> when n_IRQ may be -1. This is in practice harmless because if n_IRQ
> is -1 then we don't do anything with the src pointer, but it is
> undefined behaviour. (This has been present since this device
> was first added to QEMU.)
>
> Rearrange the code so we only do the array index when n_IRQ is not -1.
>
> Cc: qemu-stable@nongnu.org
> Fixes: e9df014c0b ("Implement embedded IRQ controller for PowerPC 6xx/740 & 75")
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> Arguable whether it's worth the stable backport or not...
> ---
> hw/intc/openpic.c | 15 ++++++++-------
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/hw/intc/openpic.c b/hw/intc/openpic.c
> index cd3d87768e0..2ead4b9ba00 100644
> --- a/hw/intc/openpic.c
> +++ b/hw/intc/openpic.c
> @@ -1031,13 +1031,14 @@ static void openpic_cpu_write_internal(void *opaque, hwaddr addr,
> s_IRQ = IRQ_get_next(opp, &dst->servicing);
> /* Check queued interrupts. */
> n_IRQ = IRQ_get_next(opp, &dst->raised);
> - src = &opp->src[n_IRQ];
> - if (n_IRQ != -1 &&
> - (s_IRQ == -1 ||
> - IVPR_PRIORITY(src->ivpr) > dst->servicing.priority)) {
> - DPRINTF("Raise OpenPIC INT output cpu %d irq %d",
> - idx, n_IRQ);
> - qemu_irq_raise(opp->dst[idx].irqs[OPENPIC_OUTPUT_INT]);
> + if (n_IRQ != -1) {
> + src = &opp->src[n_IRQ];
Could move the variable declaration here. Anyway,
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
> + if (s_IRQ == -1 ||
> + IVPR_PRIORITY(src->ivpr) > dst->servicing.priority) {
> + DPRINTF("Raise OpenPIC INT output cpu %d irq %d",
> + idx, n_IRQ);
> + qemu_irq_raise(opp->dst[idx].irqs[OPENPIC_OUTPUT_INT]);
> + }
> }
> break;
> default:
next prev parent reply other threads:[~2024-11-06 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 18:02 [PATCH] hw/intc/openpic: Avoid taking address of out-of-bounds array index Peter Maydell
2024-11-06 9:45 ` Richard Henderson [this message]
2024-11-06 11:57 ` Mark Cave-Ayland
2024-11-14 13:22 ` Peter Maydell
2024-11-14 14:35 ` Philippe Mathieu-Daudé
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=83926eb8-c5d7-4edf-b180-cc20c95a4c04@linaro.org \
--to=richard.henderson@linaro.org \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=peter.maydell@linaro.org \
--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).