From: Peter Maydell <peter.maydell@linaro.org>
To: P J P <ppandit@redhat.com>
Cc: Qemu Developers <qemu-devel@nongnu.org>,
liqsub1 <liqsub1@163.com>, Moguofang <moguofang@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v1] arm: check bit index before usage
Date: Fri, 26 Oct 2018 08:04:29 +0100 [thread overview]
Message-ID: <CAFEAcA-Mp_ovLRzHFpUCTmd6r-bmGZ2-V3OHSxo+5Mg+zw2=aA@mail.gmail.com> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1810252239320.26372@xnncv>
On 25 October 2018 at 21:31, P J P <ppandit@redhat.com> wrote:
> +-- On Thu, 25 Oct 2018, Peter Maydell wrote --+
> | Hi; thanks for this patch. Looking at the SA1110 manual,
> | it says that writes to the reserved bits [31:28] are
> | ignored. So I think that rather than doing this check
> | here, we should do what the strongarm_ppc_* code in the
> | same file does -- mask off the high bits for writes to
> | the direction and state registers. Then it will not
> | be possible for high bits to be set here that cause an
> | out-of-range array access.
>
> ===
> diff --git a/hw/arm/strongarm.c b/hw/arm/strongarm.c
> index ec2627374d..dd8c4b1f2e 100644
> --- a/hw/arm/strongarm.c
> +++ b/hw/arm/strongarm.c
> @@ -587,12 +587,12 @@ static void strongarm_gpio_write(void *opaque, hwaddr
> offset,
>
> switch (offset) {
> case GPDR: /* GPIO Pin-Direction registers */
> - s->dir = value;
> + s->dir = value & 0x3fffff;
> strongarm_gpio_handler_update(s);
> break;
>
> case GPSR: /* GPIO Pin-Output Set registers */
> - s->olevel |= value;
> + s->olevel |= value & 0x3fffff;
> strongarm_gpio_handler_update(s);
> break;
> ===
>
> does this seem okay?
Yes, that's what I had in mind.
thanks
-- PMM
next prev parent reply other threads:[~2018-10-26 7:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 18:10 [Qemu-devel] [PATCH v1] arm: check bit index before usage P J P
2018-10-22 23:23 ` Philippe Mathieu-Daudé
2018-10-23 4:51 ` P J P
2018-10-25 14:32 ` Peter Maydell
2018-10-25 20:31 ` P J P
2018-10-26 7:04 ` Peter Maydell [this message]
2018-10-26 9:37 ` P J P
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='CAFEAcA-Mp_ovLRzHFpUCTmd6r-bmGZ2-V3OHSxo+5Mg+zw2=aA@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=liqsub1@163.com \
--cc=moguofang@huawei.com \
--cc=ppandit@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).