aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/iommu/amd_iommu.c
diff options
context:
space:
mode:
authorHans de Goede <hdegoede@redhat.com>2020-03-09 19:25:10 +0100
committerJoerg Roedel <jroedel@suse.de>2020-03-13 14:25:45 +0100
commit81ee85d0462410de8eeeec1b9761941fd6ed8c7b (patch)
tree821278c99724f4a6f995412d2da2f41227fd353b /drivers/iommu/amd_iommu.c
parentiommu/vt-d: dmar_parse_one_rmrr: replace WARN_TAINT with pr_warn + add_taint (diff)
downloadlinux-dev-81ee85d0462410de8eeeec1b9761941fd6ed8c7b.tar.xz
linux-dev-81ee85d0462410de8eeeec1b9761941fd6ed8c7b.zip
iommu/vt-d: quirk_ioat_snb_local_iommu: replace WARN_TAINT with pr_warn + add_taint
Quoting from the comment describing the WARN functions in include/asm-generic/bug.h: * WARN(), WARN_ON(), WARN_ON_ONCE, and so on can be used to report * significant kernel issues that need prompt attention if they should ever * appear at runtime. * * Do not use these macros when checking for invalid external inputs The (buggy) firmware tables which the dmar code was calling WARN_TAINT for really are invalid external inputs. They are not under the kernel's control and the issues in them cannot be fixed by a kernel update. So logging a backtrace, which invites bug reports to be filed about this, is not helpful. Fixes: 556ab45f9a77 ("ioat2: catch and recover from broken vtd configurations v6") Signed-off-by: Hans de Goede <hdegoede@redhat.com> Acked-by: Lu Baolu <baolu.lu@linux.intel.com> Link: https://lore.kernel.org/r/20200309182510.373875-1-hdegoede@redhat.com BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=701847 Signed-off-by: Joerg Roedel <jroedel@suse.de>
Diffstat (limited to 'drivers/iommu/amd_iommu.c')
0 files changed, 0 insertions, 0 deletions