| commit | e33acde91140f1809952d1c135c36feb66a51887 | |
| author | Joerg Roedel <joerg.roedel@amd.com> | |
| Fri, 2 Sep 2011 12:19:50 +0000 (2 14:19 +0200) | ||
| committer | Joerg Roedel <joerg.roedel@amd.com> | |
| Fri, 2 Sep 2011 12:19:50 +0000 (2 14:19 +0200) | ||
| tree | 86c6c7d7c76a311604843e919df141c30c5b1160 | treesnapshot (tar.gz zip) |
| parent | f1ca1512e765337a7c09eb875eedef8ea4e07654 | commitdiff |
iommu/amd: Don't take domain->lock recursivly
The domain_flush_devices() function takes the domain->lock.
But this function is only called from update_domain() which
itself is already called unter the domain->lock. This causes
a deadlock situation when the dma-address-space of a domain
grows larger than 1GB.
Cc: stable@kernel.org
Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
The domain_flush_devices() function takes the domain->lock.
But this function is only called from update_domain() which
itself is already called unter the domain->lock. This causes
a deadlock situation when the dma-address-space of a domain
grows larger than 1GB.
Cc: stable@kernel.org
Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
| drivers/iommu/amd_iommu.c | diffblobblamehistory |