summaryrefslogtreecommitdiff
path: root/drivers/parport
diff options
context:
space:
mode:
authorStephen Boyd <swboyd@chromium.org>2018-10-08 00:20:07 -0700
committerChristoph Hellwig <hch@lst.de>2018-10-08 09:44:17 +0200
commit99c65fa7c59ff558e70db8aa61bbdece5d3a9588 (patch)
tree5a72a54e4d6d2104b3aeedd86d84563d2d545af5 /drivers/parport
parent1fc8e6423edb4bba365b0780c2fcddfb921b24b2 (diff)
dma-debug: Check for drivers mapping invalid addresses in dma_map_single()
I recently debugged a DMA mapping oops where a driver was trying to map a buffer returned from request_firmware() with dma_map_single(). Memory returned from request_firmware() is mapped into the vmalloc region and this isn't a valid region to map with dma_map_single() per the DMA documentation's "What memory is DMA'able?" section. Unfortunately, we don't really check that in the DMA debugging code, so enabling DMA debugging doesn't help catch this problem. Let's add a new DMA debug function to check for a vmalloc address or an invalid virtual address and print a warning if this happens. This makes it a little easier to debug these sorts of problems, instead of seeing odd behavior or crashes when drivers attempt to map the vmalloc space for DMA. Cc: Marek Szyprowski <m.szyprowski@samsung.com> Reviewed-by: Robin Murphy <robin.murphy@arm.com> Signed-off-by: Stephen Boyd <swboyd@chromium.org> Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'drivers/parport')
0 files changed, 0 insertions, 0 deletions