[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4dc8f9a4-c2cb-261e-21e7-37b2d29c7332@linux.intel.com>
Date: Wed, 21 Sep 2022 10:43:40 +0800
From: Baolu Lu <baolu.lu@...ux.intel.com>
To: iommu@...ts.linux.dev
Cc: baolu.lu@...ux.intel.com, Joerg Roedel <joro@...tes.org>,
Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>,
Kevin Tian <kevin.tian@...el.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
George Hilliard <thirtythreeforty@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] Revert "iommu/vt-d: Fix possible recursive locking in
intel_iommu_init()"
On 9/20/22 4:17 PM, Lu Baolu wrote:
> 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@...ux.intel.com>
> Reported-and-tested-by: George Hilliard<thirtythreeforty@...il.com>
> Signed-off-by: Lu Baolu<baolu.lu@...ux.intel.com>
Queued for v6.0.
https://lore.kernel.org/linux-iommu/20220921024054.3570256-1-baolu.lu@linux.intel.com
Best regards,
baolu
Powered by blists - more mailing lists