From: Joerg Roedel <joro@8bytes.org>
To: Lu Baolu <baolu.lu@linux.intel.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
Robin Murphy <robin.murphy@arm.com>,
iommu@lists.linux.dev, iommu@lists.linux-foundation.org
Subject: Re: [PATCH 0/1] iommu/vt-d: Fixes for v6.0-rc5
Date: Sun, 11 Sep 2022 08:25:42 +0200 [thread overview]
Message-ID: <Yx1/ZolNr6IetMoz@8bytes.org> (raw)
In-Reply-To: <20220911031845.893192-1-baolu.lu@linux.intel.com>
On Sun, Sep 11, 2022 at 11:18:44AM +0800, Lu Baolu wrote:
> Below fix is queued for v6.0-rc5. It aim to fix:
>
> - Fix possible recursive locking in intel_iommu_init().
>
> It also eliminates the issue highlighted in commit c919739ce4721
> ("iommu/vt-d: Handle race between registration and device probe"),
> which has been pushed to linux next.
>
> Please consider it for the iommu/fix branch.
>
> Best regards,
> Lu Baolu
>
> Lu Baolu (1):
> iommu/vt-d: Fix possible recursive locking in intel_iommu_init()
Applied, thanks Baolu.
prev parent reply other threads:[~2022-09-11 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 3:18 [PATCH 0/1] iommu/vt-d: Fixes for v6.0-rc5 Lu Baolu
2022-09-11 3:18 ` [PATCH 1/1] iommu/vt-d: Fix possible recursive locking in intel_iommu_init() Lu Baolu
2022-09-11 6:25 ` Joerg Roedel [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=Yx1/ZolNr6IetMoz@8bytes.org \
--to=joro@8bytes.org \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=robin.murphy@arm.com \
/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