summaryrefslogtreecommitdiff
path: root/kernel/time
diff options
context:
space:
mode:
authorLu Baolu <baolu.lu@linux.intel.com>2022-09-21 10:40:53 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2022-09-23 14:14:06 +0200
commit4d8637f1d67242207410734844ca4b143ac5585e (patch)
tree9b1061514317e693aa0b8a49b629d0d59fc32d2a /kernel/time
parent36371c3adb7a2fd25bce781077763fa3dad44712 (diff)
downloadlinux-4d8637f1d67242207410734844ca4b143ac5585e.tar.gz
linux-4d8637f1d67242207410734844ca4b143ac5585e.tar.bz2
linux-4d8637f1d67242207410734844ca4b143ac5585e.zip
Revert "iommu/vt-d: Fix possible recursive locking in intel_iommu_init()"
commit 7ebb5f8e001037efbdf18afabbbebf71bd98825e upstream. This reverts commit 9cd4f1434479f1ac25c440c421fbf52069079914. Some issues were reported on the original commit. Some thunderbolt devices don't work anymore due to the following DMA fault. DMAR: DRHD: handling fault status reg 2 DMAR: [INTR-REMAP] Request device [09:00.0] fault index 0x8080 [fault reason 0x25] Blocked a compatibility format interrupt request Bring it back for now to avoid functional regression. Fixes: 9cd4f1434479f ("iommu/vt-d: Fix possible recursive locking in intel_iommu_init()") Link: https://lore.kernel.org/linux-iommu/485A6EA5-6D58-42EA-B298-8571E97422DE@getmailspring.com/ Link: https://bugzilla.kernel.org/show_bug.cgi?id=216497 Cc: Mika Westerberg <mika.westerberg@linux.intel.com> Cc: <stable@vger.kernel.org> # 5.19.x Reported-and-tested-by: George Hilliard <thirtythreeforty@gmail.com> Signed-off-by: Lu Baolu <baolu.lu@linux.intel.com> Link: https://lore.kernel.org/r/20220920081701.3453504-1-baolu.lu@linux.intel.com Signed-off-by: Joerg Roedel <jroedel@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/time')
0 files changed, 0 insertions, 0 deletions