diff options
author | Joerg Roedel <jroedel@suse.de> | 2014-08-05 17:50:15 +0200 |
---|---|---|
committer | Joerg Roedel <jroedel@suse.de> | 2014-08-18 13:37:56 +0200 |
commit | 9b29d3c6510407d91786c1cf9183ff4debb3473a (patch) | |
tree | 6ba5f79299a91bd4f697800b3c8ae66bb444caec /drivers/iommu | |
parent | e7f9fa5498d91fcdc63d93007ba43f36b1a30538 (diff) | |
download | linux-9b29d3c6510407d91786c1cf9183ff4debb3473a.tar.gz linux-9b29d3c6510407d91786c1cf9183ff4debb3473a.tar.xz |
iommu/amd: Fix cleanup_domain for mass device removal
When multiple devices are detached in __detach_device, they
are also removed from the domains dev_list. This makes it
unsafe to use list_for_each_entry_safe, as the next pointer
might also not be in the list anymore after __detach_device
returns. So just repeatedly remove the first element of the
list until it is empty.
Cc: stable@vger.kernel.org
Tested-by: Marti Raudsepp <marti@juffo.org>
Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'drivers/iommu')
-rw-r--r-- | drivers/iommu/amd_iommu.c | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c index 18405314168b..ecb0109a5360 100644 --- a/drivers/iommu/amd_iommu.c +++ b/drivers/iommu/amd_iommu.c @@ -3149,14 +3149,16 @@ free_domains: static void cleanup_domain(struct protection_domain *domain) { - struct iommu_dev_data *dev_data, *next; + struct iommu_dev_data *entry; unsigned long flags; write_lock_irqsave(&amd_iommu_devtable_lock, flags); - list_for_each_entry_safe(dev_data, next, &domain->dev_list, list) { - __detach_device(dev_data); - atomic_set(&dev_data->bind, 0); + while (!list_empty(&domain->dev_list)) { + entry = list_first_entry(&domain->dev_list, + struct iommu_dev_data, list); + __detach_device(entry); + atomic_set(&entry->bind, 0); } write_unlock_irqrestore(&amd_iommu_devtable_lock, flags); |