summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorDavid Brownell <david-b@pacbell.net>2005-05-28 10:46:18 -0700
committerGreg Kroah-Hartman <gregkh@suse.de>2005-06-27 14:44:00 -0700
commit77078570abe0848c3076b4f7d42f79b1407f3e8f (patch)
tree47b421662c3c2e18cfe0bdf95c0a1ef42d89abb2 /kernel
parente07fefa6b212f43c40fdbc1a62de690d91a4b617 (diff)
downloadop-kernel-dev-77078570abe0848c3076b4f7d42f79b1407f3e8f.zip
op-kernel-dev-77078570abe0848c3076b4f7d42f79b1407f3e8f.tar.gz
[PATCH] USB: ehci-hcd - fix page pointer allocation in itd_patch()
The itd_patch() function is responsible for allocating entries in the buffer page pointer list of the iTD. Particularly, a new page pointer is needed every time when buffer data crosses a page boundary. However, there is a bug in the allocation logic: the function does not allocate a new entry when the current transaction is the first transaction in the iTD (as indicated by first!=0). The consequence is that, when the data of the first transaction begins somewhere at the end of a page so that it actually does cross the page boundary, no new page pointer is allocated. This means that the data at the end of the first transaction (beyond the page boundary) will be accessed by the HC using the second page pointer, which is zero. Furthermore, the first page pointer will be later overwritten by the page pointers of the other transactions, which will garble it because the value is or-ed into the iTD field. All this particular check (for !first) does is cause incorrect behaviour, so it should be entirely removed (and with it the variable first that is not used for anything else). Signed-off-by: Clemens Ladisch <clemens@ladisch.de> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud