From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>, Andriy Gapon <avg@FreeBSD.org>
Subject: [Qemu-devel] [PATCH 4/4] usb-ohci: td.cbp incorrectly updated near page end
Date: Fri, 6 Jan 2012 13:50:32 +0100 [thread overview]
Message-ID: <1325854232-17478-5-git-send-email-kraxel@redhat.com> (raw)
In-Reply-To: <1325854232-17478-1-git-send-email-kraxel@redhat.com>
From: Andriy Gapon <avg@FreeBSD.org>
The current code that updates the cbp value after a transfer looks like this:
td.cbp += ret;
if ((td.cbp & 0xfff) + ret > 0xfff) {
<handle page overflow>
because the 'ret' value is effectively added twice the check may fire too early
when the overflow hasn't happened yet.
Below is one of the possible changes that correct the behavior:
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
hw/usb-ohci.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/hw/usb-ohci.c b/hw/usb-ohci.c
index e68be70..81488c4 100644
--- a/hw/usb-ohci.c
+++ b/hw/usb-ohci.c
@@ -1025,10 +1025,10 @@ static int ohci_service_td(OHCIState *ohci, struct ohci_ed *ed)
if (ret == len) {
td.cbp = 0;
} else {
- td.cbp += ret;
if ((td.cbp & 0xfff) + ret > 0xfff) {
- td.cbp &= 0xfff;
- td.cbp |= td.be & ~0xfff;
+ td.cbp = (td.be & ~0xfff) + ((td.cbp + ret) & 0xfff);
+ } else {
+ td.cbp += ret;
}
}
td.flags |= OHCI_TD_T1;
--
1.7.1
next prev parent reply other threads:[~2012-01-06 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 12:50 [Qemu-devel] [PULL] usb bugfix patch queue Gerd Hoffmann
2012-01-06 12:50 ` [Qemu-devel] [PATCH 1/4] Fix parse of usb device description with multiple configurations Gerd Hoffmann
2012-01-06 12:50 ` [Qemu-devel] [PATCH 2/4] usb-storage: cancel I/O on reset Gerd Hoffmann
2012-01-06 12:50 ` [Qemu-devel] [PATCH 3/4] usb-host: properly release port on unplug & exit Gerd Hoffmann
2012-01-06 12:50 ` Gerd Hoffmann [this message]
2012-01-09 14:52 ` [Qemu-devel] [PULL] usb bugfix patch queue Anthony Liguori
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=1325854232-17478-5-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=avg@FreeBSD.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).