From: Alon Levy <alevy@redhat.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] usb-ehci: Ensure frindex writes leave a valid frindex value
Date: Tue, 3 Apr 2012 16:16:02 +0300 [thread overview]
Message-ID: <20120403131602.GQ20067@garlic.redhat.com> (raw)
In-Reply-To: <1333455707-3534-1-git-send-email-hdegoede@redhat.com>
On Tue, Apr 03, 2012 at 02:21:47PM +0200, Hans de Goede wrote:
> frindex is a 14 bits counter, so bits 31-14 should always be 0, and
> after the commit titled "usb-ehci: frindex always is a 14 bits counter"
> we rely on frindex always being a multiple of 8. I've not seen this in
> practice, but theoretically a guest can write a value >= 0x4000 or a value
> which is not a multiple of 8 value to frindex, this patch ensures that
> things will still work when that happens.
Acked-by: Alon Levy <alevy@redhat.com>
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
> ---
> hw/usb/hcd-ehci.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/hw/usb/hcd-ehci.c b/hw/usb/hcd-ehci.c
> index 64b58e3..8865b4e 100644
> --- a/hw/usb/hcd-ehci.c
> +++ b/hw/usb/hcd-ehci.c
> @@ -1102,6 +1102,10 @@ static void ehci_mem_writel(void *ptr, target_phys_addr_t addr, uint32_t val)
> val &= USBINTR_MASK;
> break;
>
> + case FRINDEX:
> + val &= 0x00003ff8; /* frindex is 14bits and always a multiple of 8 */
> + break;
> +
> case CONFIGFLAG:
> val &= 0x1;
> if (val) {
> --
> 1.7.9.3
>
>
next prev parent reply other threads:[~2012-04-03 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 12:21 [Qemu-devel] [PATCH] usb-ehci: Ensure frindex writes leave a valid frindex value Hans de Goede
2012-04-03 13:16 ` Alon Levy [this message]
2012-04-03 13:33 ` Alon Levy
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=20120403131602.GQ20067@garlic.redhat.com \
--to=alevy@redhat.com \
--cc=hdegoede@redhat.com \
--cc=kraxel@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).