summaryrefslogtreecommitdiffstats
path: root/drivers/usb/host/isp1760-hcd.c
diff options
context:
space:
mode:
authorStephen Warren <swarren@nvidia.com>2013-05-08 00:53:52 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-05-17 02:30:52 +0200
commit3b9561e9d9b88eca9d4ed6aab025dec2eeeed501 (patch)
tree6ac9d662f3b7c4ee4411d4fc5103f1226430740a /drivers/usb/host/isp1760-hcd.c
parentUSB: Blacklisted Cinterion's PLxx WWAN Interface (diff)
downloadlinux-3b9561e9d9b88eca9d4ed6aab025dec2eeeed501.tar.xz
linux-3b9561e9d9b88eca9d4ed6aab025dec2eeeed501.zip
USB: set device dma_mask without reference to global data
Many USB host drivers contain code such as: if (!pdev->dev.dma_mask) pdev->dev.dma_mask = &tegra_ehci_dma_mask; ... where tegra_ehci_dma_mask is a global. I suspect this code originated in commit 4a53f4e "USB: ehci-tegra: add probing through device tree" and was simply copied everywhere else. This works fine when the code is built-in, but can cause a crash when the code is in a module. The first module load sets up the dma_mask pointer, but if the module is removed and re-inserted, the value is now non-NULL, and hence is not updated to point at the new location, and hence points at a stale location within the previous module load address, which in turn causes a crash if the pointer is de-referenced. The simplest way of solving this seems to be to copy the code from ehci-platform.c, which uses the coherent_dma_mask as the target for the dma_mask pointer. Suggested-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Stephen Warren <swarren@nvidia.com> Acked-by: Tony Prisk <linux@prisktech.co.nz> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/usb/host/isp1760-hcd.c')
0 files changed, 0 insertions, 0 deletions