aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorLogan Gunthorpe <logang@deltatee.com>2019-12-16 12:01:16 -0700
committerVinod Koul <vkoul@kernel.org>2019-12-24 10:18:32 +0530
commitdae7a589c18a4d979d5f14b09374e871b995ceb1 (patch)
treeb788a32e2ed73ecd8fbe3961f95456b2b9dc66e9 /tools/perf/scripts/python
parentdmaengine: JZ4780: Add support for the X1830. (diff)
downloadlinux-dae7a589c18a4d979d5f14b09374e871b995ceb1.tar.gz
linux-dae7a589c18a4d979d5f14b09374e871b995ceb1.zip
dmaengine: Store module owner in dma_device struct
dma_chan_to_owner() dereferences the driver from the struct device to obtain the owner and call module_[get|put](). However, if the backing device is unbound before the dma_device is unregistered, the driver will be cleared and this will cause a NULL pointer dereference. Instead, store a pointer to the owner module in the dma_device struct so the module reference can be properly put when the channel is put, even if the backing device was destroyed first. This change helps to support a safer unbind of DMA engines. If the dma_device is unregistered in the driver's remove function, there's no guarantee that there are no existing clients and a users action may trigger the WARN_ONCE in dma_async_device_unregister() which is unlikely to leave the system in a consistent state. Instead, a better approach is to allow the backing driver to go away and fail any subsequent requests to it. Signed-off-by: Logan Gunthorpe <logang@deltatee.com> Link: https://lore.kernel.org/r/20191216190120.21374-2-logang@deltatee.com Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions