From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: "Zhenzhong Duan" <zhenzhong.duan@intel.com>,
"Naval Alcalá" <ari@naval.cat>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] [PULL REQUEST] iommu/vt-d: Fixes for v7.1-rc
Date: Sat, 9 May 2026 10:43:43 +0800 [thread overview]
Message-ID: <20260509024348.3516523-1-baolu.lu@linux.intel.com> (raw)
Hi Joerg,
The following fixes have been queued for v7.1-rc. They aim to fix the
following issues.
- Apply an existing quirk for Q35 graphic device.
- Skip dev_pasid teardown for the blocked domain to avoid out-of-bounds
access.
- Return early if dev_pasid is missing to prevent NULL dereference or
UAF.
These patches have been reviewed and tested and are ready for merge.
Please consider them for iommu/fix branch.
Best regards,
baolu
Naval Alcalá (1):
iommu/vt-d: Disable DMAR for Intel Q35 IGFX
Zhenzhong Duan (2):
iommu/vt-d: Fix oops due to out of scope access
iommu/vt-d: Avoid NULL pointer dereference or refcount corruption
drivers/iommu/intel/iommu.c | 16 ++++++++++------
1 file changed, 10 insertions(+), 6 deletions(-)
--
2.43.0
next reply other threads:[~2026-05-09 2:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 2:43 Lu Baolu [this message]
2026-05-09 2:43 ` [PATCH 1/3] iommu/vt-d: Disable DMAR for Intel Q35 IGFX Lu Baolu
2026-05-09 2:43 ` [PATCH 2/3] iommu/vt-d: Fix oops due to out of scope access Lu Baolu
2026-05-09 2:43 ` [PATCH 3/3] iommu/vt-d: Avoid NULL pointer dereference or refcount corruption Lu Baolu
2026-05-11 8:20 ` [PATCH 0/3] [PULL REQUEST] iommu/vt-d: Fixes for v7.1-rc Joerg Roedel
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=20260509024348.3516523-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ari@naval.cat \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zhenzhong.duan@intel.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