aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSheng Yang <sheng@linux.intel.com>2009-07-08 06:52:52 -0400
committerLinus Torvalds <torvalds@linux-foundation.org>2009-07-08 12:35:10 -0400
commit4b99d3527041bec1abe9903263a3a1b7d2ba0c4a (patch)
treec28eb8558d7cdc56607f9eff4c8073928b32d202
parent0f2f2221b4ad816567394a52643963428fd353cd (diff)
intel-iommu: Fix intel_iommu_unmap_range() with size 0
After some API change, intel_iommu_unmap_range() introduced a assumption that parameter size != 0, otherwise the dma_pte_clean_range() would have a overflowed argument. But the user like KVM don't have this assumption before, then some BUG() triggered. Fix it by ignoring size = 0. Signed-off-by: Sheng Yang <sheng@linux.intel.com> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
-rw-r--r--drivers/pci/intel-iommu.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/pci/intel-iommu.c b/drivers/pci/intel-iommu.c
index 360fb67a30d7..ebc9b8dca881 100644
--- a/drivers/pci/intel-iommu.c
+++ b/drivers/pci/intel-iommu.c
@@ -3600,6 +3600,9 @@ static void intel_iommu_unmap_range(struct iommu_domain *domain,
3600{ 3600{
3601 struct dmar_domain *dmar_domain = domain->priv; 3601 struct dmar_domain *dmar_domain = domain->priv;
3602 3602
3603 if (!size)
3604 return;
3605
3603 dma_pte_clear_range(dmar_domain, iova >> VTD_PAGE_SHIFT, 3606 dma_pte_clear_range(dmar_domain, iova >> VTD_PAGE_SHIFT,
3604 (iova + size - 1) >> VTD_PAGE_SHIFT); 3607 (iova + size - 1) >> VTD_PAGE_SHIFT);
3605 3608