| commit | 020d1eecf345422d34bec8fb4a45299dcc0dcc3f | |
| author | David Woodhouse <David.Woodhouse@intel.com> | |
| Wed, 2 Dec 2009 10:18:30 +0000 (2 10:18 +0000) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Fri, 18 Dec 2009 22:05:57 +0000 (18 14:05 -0800) | ||
| tree | 4d030e2bc03dcdb079ab3d607588942454d97e34 | treesnapshot (tar.gz zip) |
| parent | 39035f9c09699eea2dd154d170919dcd41c6885d | commitdiff |
intel-iommu: Fix oops with intel_iommu=igfx_off
commit 44cd613c0e4cd93079ea2a93aa06649d8ca0830a upstream.
The hotplug notifier will call find_domain() to see if the device in
question has been assigned an IOMMU domain. However, this should never
be called for devices with a "dummy" domain, such as graphics devices
when intel_iommu=igfx_off is set and the corresponding IOMMU isn't even
initialised. If you do that, it'll oops as it dereferences the (-1)
pointer.
The notifier function should check iommu_no_mapping() for the
device before doing anything else.
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit 44cd613c0e4cd93079ea2a93aa06649d8ca0830a upstream.
The hotplug notifier will call find_domain() to see if the device in
question has been assigned an IOMMU domain. However, this should never
be called for devices with a "dummy" domain, such as graphics devices
when intel_iommu=igfx_off is set and the corresponding IOMMU isn't even
initialised. If you do that, it'll oops as it dereferences the (-1)
pointer.
The notifier function should check iommu_no_mapping() for the
device before doing anything else.
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/pci/intel-iommu.c | diffblobblamehistory |