Re: [PATCH 2/2] dma-debug: Update DMA debug API to better handle multiple mappings of a buffer

On Mon, 2013-03-18 at 15:12 -0700, Alexander Duyck wrote: > There were reports of the igb driver unmapping buffers without calling > dma_mapping_error. On closer inspection issues were found in the DMA debug > API and how it handled multiple mappings of the same buffer. > > The issue I found is

Re: [PATCH 2/2] dma-debug: Update DMA debug API to better handle multiple mappings of a buffer

On Mon, 2013-03-18 at 15:12 -0700, Alexander Duyck wrote: There were reports of the igb driver unmapping buffers without calling dma_mapping_error. On closer inspection issues were found in the DMA debug API and how it handled multiple mappings of the same buffer. The issue I found is the

[PATCH 2/2] dma-debug: Update DMA debug API to better handle multiple mappings of a buffer

There were reports of the igb driver unmapping buffers without calling dma_mapping_error. On closer inspection issues were found in the DMA debug API and how it handled multiple mappings of the same buffer. The issue I found is the fact that the debug_dma_mapping_error would only set the

[PATCH 2/2] dma-debug: Update DMA debug API to better handle multiple mappings of a buffer

There were reports of the igb driver unmapping buffers without calling dma_mapping_error. On closer inspection issues were found in the DMA debug API and how it handled multiple mappings of the same buffer. The issue I found is the fact that the debug_dma_mapping_error would only set the