Re: dma_ops_domain_alloc causes kernel 4.1.0-next-20150626+ panic

[Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>]

On Tue, Jun 30, 2015 at 01:44:34AM +0800, George Wang wrote:
> diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
> index d3e5e9a..4f6da17 100644
> --- a/drivers/iommu/amd_iommu.c
> +++ b/drivers/iommu/amd_iommu.c
> @@ -1882,6 +1882,7 @@ static struct dma_ops_domain *dma_ops_domain_alloc(void)
>                 return NULL;
> 
>         spin_lock_init(&dma_dom->domain.lock);
> +       mutex_init(&dma_dom->domain.api_lock);
> 
> When I initialize the api_lock, then I can go forward with another problem.

How do you trigger this? The DMA-API domains are not used via the
IOMMU-API yet, so the initializing the api-lock for it shouldn't matter.


	Joerg