From: Aurelien Jarno <aurelien@aurel32.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] array overflow in hw/stellaris.c and hw/omap_dss.c
Date: Fri, 22 Aug 2008 11:01:16 +0200 [thread overview]
Message-ID: <20080822090116.GD21526@volta.aurel32.net> (raw)
In-Reply-To: <20080705104822.377b403d@holly>
On Sat, Jul 05, 2008 at 10:48:22AM +0200, Jindrich Makovicka wrote:
> Hi,
>
> there are some under-dimensioned arrays in $subj.
>
Applied, thanks.
> Index: stellaris.c
> ===================================================================
> --- stellaris.c (revision 4846)
> +++ stellaris.c (working copy)
> @@ -1308,8 +1308,8 @@
> static const int gpio_irq[7] = {0, 1, 2, 3, 4, 30, 31};
>
> qemu_irq *pic;
> - qemu_irq *gpio_in[5];
> - qemu_irq *gpio_out[5];
> + qemu_irq *gpio_in[7];
> + qemu_irq *gpio_out[7];
> qemu_irq adc;
> int sram_size;
> int flash_size;
> Index: omap_dss.c
> ===================================================================
> --- omap_dss.c (revision 4846)
> +++ omap_dss.c (working copy)
> @@ -53,7 +53,7 @@
> uint32_t control;
> uint32_t config;
> uint32_t capable;
> - uint32_t timing[3];
> + uint32_t timing[4];
> int line;
> uint32_t bg[2];
> uint32_t trans[2];
> @@ -148,6 +148,7 @@
> s->dispc.timing[0] = 0;
> s->dispc.timing[1] = 0;
> s->dispc.timing[2] = 0;
> + s->dispc.timing[3] = 0;
> s->dispc.line = 0;
> s->dispc.bg[0] = 0;
> s->dispc.bg[1] = 0;
>
> Regards,
> --
> Jindrich Makovicka
>
>
>
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' aurel32@debian.org | aurelien@aurel32.net
`- people.debian.org/~aurel32 | www.aurel32.net
prev parent reply other threads:[~2008-08-22 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 8:48 [Qemu-devel] array overflow in hw/stellaris.c and hw/omap_dss.c Jindrich Makovicka
2008-08-22 9:01 ` Aurelien Jarno [this message]
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=20080822090116.GD21526@volta.aurel32.net \
--to=aurelien@aurel32.net \
--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).