diff options
| author | Zhenzhong Duan <zhenzhong.duan@gmail.com> | 2020-11-10 15:19:08 +0800 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2020-11-24 13:39:04 +0100 |
| commit | 3330e9f177a6278d7328b01ac5676396851891a5 (patch) | |
| tree | 85ed4591ab40ef563bbfb49331a17b3fa515a563 /security/inode.c | |
| parent | 5528e3d431bdee64edaafc6df8266f4f3c0975ce (diff) | |
| download | linux-stable-3330e9f177a6278d7328b01ac5676396851891a5.tar.gz linux-stable-3330e9f177a6278d7328b01ac5676396851891a5.tar.bz2 linux-stable-3330e9f177a6278d7328b01ac5676396851891a5.zip | |
iommu/vt-d: Avoid panic if iommu init fails in tboot system
[ Upstream commit 4d213e76a359e540ca786ee937da7f35faa8e5f8 ]
"intel_iommu=off" command line is used to disable iommu but iommu is force
enabled in a tboot system for security reason.
However for better performance on high speed network device, a new option
"intel_iommu=tboot_noforce" is introduced to disable the force on.
By default kernel should panic if iommu init fail in tboot for security
reason, but it's unnecessory if we use "intel_iommu=tboot_noforce,off".
Fix the code setting force_on and move intel_iommu_tboot_noforce
from tboot code to intel iommu code.
Fixes: 7304e8f28bb2 ("iommu/vt-d: Correctly disable Intel IOMMU force on")
Signed-off-by: Zhenzhong Duan <zhenzhong.duan@gmail.com>
Tested-by: Lukasz Hawrylko <lukasz.hawrylko@linux.intel.com>
Acked-by: Lu Baolu <baolu.lu@linux.intel.com>
Link: https://lore.kernel.org/r/20201110071908.3133-1-zhenzhong.duan@gmail.com
Signed-off-by: Will Deacon <will@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'security/inode.c')
0 files changed, 0 insertions, 0 deletions