Re: [PATCH] iommu/dma: Don't put uninitialised IOVA domains

2016-08-09 Thread Robin Murphy
On 09/08/16 16:01, Joerg Roedel wrote: > On Wed, Jul 27, 2016 at 04:46:06PM +0100, Robin Murphy wrote: >> Due to the limitations of having to wait until we see a device's DMA >> restrictions before we know how we want an IOVA domain initialised, >> there is a window for error if a DMA ops domain

Re: [PATCH] iommu/dma: Don't put uninitialised IOVA domains

2016-08-09 Thread Joerg Roedel
On Wed, Jul 27, 2016 at 04:46:06PM +0100, Robin Murphy wrote: > Due to the limitations of having to wait until we see a device's DMA > restrictions before we know how we want an IOVA domain initialised, > there is a window for error if a DMA ops domain is allocated but later > freed without ever

Re: [PATCH] iommu/dma: Don't put uninitialised IOVA domains

2016-07-27 Thread nwatters
On 2016-07-27 12:00, Auger Eric wrote: Hi, On 27/07/2016 17:46, Robin Murphy wrote: Due to the limitations of having to wait until we see a device's DMA restrictions before we know how we want an IOVA domain initialised, there is a window for error if a DMA ops domain is allocated but later

Re: [PATCH] iommu/dma: Don't put uninitialised IOVA domains

2016-07-27 Thread Auger Eric
Hi, On 27/07/2016 17:46, Robin Murphy wrote: > Due to the limitations of having to wait until we see a device's DMA > restrictions before we know how we want an IOVA domain initialised, > there is a window for error if a DMA ops domain is allocated but later > freed without ever being used. In