Re: [RESEND PATCH] ioatdma, fix dma mapping errors

2014-12-09 Thread Vinod Koul
On Thu, Oct 23, 2014 at 07:38:29AM -0400, Prarit Bhargava wrote: > This happens because the current ioatdma DMA test code does not check the > return > value of dma_map_page() calls with dma_mapping_error(). In addition, it was > noticed that mapping for the variable dest_dma is free'd before the

Re: [RESEND PATCH] ioatdma, fix dma mapping errors

2014-11-12 Thread Prarit Bhargava
On 11/12/2014 04:43 AM, Vinod Koul wrote: > On Thu, Oct 23, 2014 at 06:36:58AM -0700, Dan Williams wrote: >> On Thu, Oct 23, 2014 at 4:38 AM, Prarit Bhargava wrote: >>> No response from anyone the first time ... >>> >> >> Sorry about that, thanks for re-posting. >> >> >> Dave, can you check this

Re: [RESEND PATCH] ioatdma, fix dma mapping errors

2014-11-12 Thread Vinod Koul
On Thu, Oct 23, 2014 at 06:36:58AM -0700, Dan Williams wrote: > On Thu, Oct 23, 2014 at 4:38 AM, Prarit Bhargava wrote: > > No response from anyone the first time ... > > > > Sorry about that, thanks for re-posting. > > > Dave, can you check this out / ack so Vinod can take this? I dont think

Re: [RESEND PATCH] ioatdma, fix dma mapping errors

2014-10-23 Thread Dan Williams
On Thu, Oct 23, 2014 at 4:38 AM, Prarit Bhargava wrote: > No response from anyone the first time ... > Sorry about that, thanks for re-posting. > P. > > 8< > > Several systems are showing the following stack trace: > > WARNING: CPU: 0 PID: 2352 at lib/dma-debug.c:1140 check_unmap+0x4ee/0

[RESEND PATCH] ioatdma, fix dma mapping errors

2014-10-23 Thread Prarit Bhargava
No response from anyone the first time ... P. 8< Several systems are showing the following stack trace: WARNING: CPU: 0 PID: 2352 at lib/dma-debug.c:1140 check_unmap+0x4ee/0x9e0() ioatdma :00:04.0: DMA-API: device driver failed to check map error[device address=0x000465bad000]