USB: Fix 'bad dma' problem on WDM device disconnect
authorRobert Lukassen <Robert.Lukassen@tomtom.com>
Wed, 16 Mar 2011 11:13:34 +0000 (12:13 +0100)
committerGreg Kroah-Hartman <gregkh@suse.de>
Wed, 23 Mar 2011 20:21:02 +0000 (13:21 -0700)
commit878b753e32ca765cd346a5d3038d630178ec78ff
tree0b72c2d333471c292d7b30ef675302f1205022df
parent97ac01d8f1b8d1c9e5af32c2813ba771835961f9
USB: Fix 'bad dma' problem on WDM device disconnect

In the WDM class driver a disconnect event leads to calls to
usb_free_coherent to put back two USB DMA buffers allocated earlier.
The call to usb_free_coherent uses a different size parameter
(desc->wMaxCommand) than the corresponding call to usb_alloc_coherent
(desc->bMaxPacketSize0).

When a disconnect event occurs, this leads to 'bad dma' complaints
from usb core because the USB DMA buffer is being pushed back to the
'buffer-2048' pool from which it has not been allocated.

This patch against the most recent linux-2.6 kernel ensures that the
parameters used by usb_alloc_coherent & usb_free_coherent calls in
cdc-wdm.c match.

Signed-off-by: Robert Lukassen <robert.lukassen@tomtom.com>
Cc: stable <stable@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
drivers/usb/class/cdc-wdm.c