From: Baolu Lu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>
Cc: baolu.lu@linux.intel.com, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] iommu/vt-d: Fixes for issues reported by Sashiko
Date: Tue, 4 Aug 2026 10:28:31 +0800 [thread overview]
Message-ID: <af65db88-23e2-4c74-bfde-13587da360f0@linux.intel.com> (raw)
In-Reply-To: <20260731054329.2948252-1-baolu.lu@linux.intel.com>
On 7/31/2026 1:43 PM, Lu Baolu wrote:
> Hi,
>
> This collects a number of pre-existing issues that were reported by
> Sashiko while reviewing recent VT-d patches. None of them are
> regressions from the patches under review; they are latent problems in
> code those patches happened to touch. They are independent of each other
> and can be applied in any order.
>
> Thanks,
> baolu
>
> Lu Baolu (5):
> iommu/vt-d: Fix shift overflow in qi_desc_dev_iotlb_pasid()
> iommu/vt-d: Clear Present bit before tearing down copied context entry
> iommu/vt-d: Fix iopf_refcount leak on RID domain replacement
> iommu/vt-d: Tear down scalable-mode context on probe failure
> iommu/vt-d: Flush context cache with correct SID when tearing down
> aliases
>
> drivers/iommu/intel/iommu.h | 18 +++++++++++++-----
> drivers/iommu/intel/iommu.c | 22 +++++++++++++++-------
> drivers/iommu/intel/pasid.c | 9 ++++++---
> 3 files changed, 34 insertions(+), 15 deletions(-)
Queued for iommu/vt-d.
prev parent reply other threads:[~2026-08-04 2:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 5:43 [PATCH 0/5] iommu/vt-d: Fixes for issues reported by Sashiko Lu Baolu
2026-07-31 5:43 ` [PATCH 1/5] iommu/vt-d: Fix shift overflow in qi_desc_dev_iotlb_pasid() Lu Baolu
2026-08-03 18:28 ` Samiullah Khawaja
2026-07-31 5:43 ` [PATCH 2/5] iommu/vt-d: Clear Present bit before tearing down copied context entry Lu Baolu
2026-07-31 5:43 ` [PATCH 3/5] iommu/vt-d: Fix iopf_refcount leak on RID domain replacement Lu Baolu
2026-07-31 5:43 ` [PATCH 4/5] iommu/vt-d: Tear down scalable-mode context on probe failure Lu Baolu
2026-07-31 5:43 ` [PATCH 5/5] iommu/vt-d: Flush context cache with correct SID when tearing down aliases Lu Baolu
2026-08-03 18:19 ` Samiullah Khawaja
2026-08-04 2:28 ` 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=af65db88-23e2-4c74-bfde-13587da360f0@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.