From: Baolu Lu <baolu.lu@linux.intel.com>
To: iommu@lists.linux.dev
Cc: baolu.lu@linux.intel.com, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Kevin Tian <kevin.tian@intel.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
George Hilliard <thirtythreeforty@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Revert "iommu/vt-d: Fix possible recursive locking in intel_iommu_init()"
Date: Wed, 21 Sep 2022 10:43:40 +0800 [thread overview]
Message-ID: <4dc8f9a4-c2cb-261e-21e7-37b2d29c7332@linux.intel.com> (raw)
In-Reply-To: <20220920081701.3453504-1-baolu.lu@linux.intel.com>
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@linux.intel.com>
> Reported-and-tested-by: George Hilliard<thirtythreeforty@gmail.com>
> Signed-off-by: Lu Baolu<baolu.lu@linux.intel.com>
Queued for v6.0.
https://lore.kernel.org/linux-iommu/20220921024054.3570256-1-baolu.lu@linux.intel.com
Best regards,
baolu
prev parent reply other threads:[~2022-09-21 2:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 8:17 [PATCH 1/1] Revert "iommu/vt-d: Fix possible recursive locking in intel_iommu_init()" Lu Baolu
2022-09-20 11:58 ` Thorsten Leemhuis
2022-09-20 12:16 ` Robin Murphy
2022-09-20 12:36 ` Baolu Lu
2022-09-21 2:43 ` Baolu Lu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4dc8f9a4-c2cb-261e-21e7-37b2d29c7332@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=robin.murphy@arm.com \
--cc=thirtythreeforty@gmail.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox