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.

Thanks,
baolu

Lu Baolu (7):
  iommu/vt-d: Avoid out-of-range shift in qi_desc_dev_iotlb_pasid()
  iommu/vt-d: Do not ignore context table copy failures
  iommu/vt-d: Handle DID reservation errors when copying context tables
  iommu/vt-d: Reserve scalable-mode DIDs from PASID entries during copy
  iommu/vt-d: Use old domain parameter when attaching the blocking
    domain
  iommu/vt-d: Fix iopf refcount leak in nested attach
  iommu/vt-d: Drop old iopf ref only after attach succeeds

 drivers/iommu/intel/iommu.h  |  17 +++-
 drivers/iommu/intel/iommu.c  | 152 ++++++++++++++++++++++++++++++-----
 drivers/iommu/intel/nested.c |   2 +
 3 files changed, 149 insertions(+), 22 deletions(-)

-- 
2.43.0

On 9/9/26 15:50, 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.
> 
> Thanks,
> baolu
> 
> Lu Baolu (7):
>    iommu/vt-d: Avoid out-of-range shift in qi_desc_dev_iotlb_pasid()
>    iommu/vt-d: Do not ignore context table copy failures
>    iommu/vt-d: Handle DID reservation errors when copying context tables
>    iommu/vt-d: Reserve scalable-mode DIDs from PASID entries during copy
>    iommu/vt-d: Use old domain parameter when attaching the blocking
>      domain
>    iommu/vt-d: Fix iopf refcount leak in nested attach
>    iommu/vt-d: Drop old iopf ref only after attach succeeds
> 
>   drivers/iommu/intel/iommu.h  |  17 +++-
>   drivers/iommu/intel/iommu.c  | 152 ++++++++++++++++++++++++++++++-----
>   drivers/iommu/intel/nested.c |   2 +
>   3 files changed, 149 insertions(+), 22 deletions(-)

Queued for iommu/next.

> From: Lu Baolu <baolu.lu@linux.intel.com>
> Sent: Wednesday, September 9, 2026 3:51 PM
> 
> 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.
> 
> Thanks,
> baolu
> 
> Lu Baolu (7):
>   iommu/vt-d: Avoid out-of-range shift in qi_desc_dev_iotlb_pasid()
>   iommu/vt-d: Do not ignore context table copy failures
>   iommu/vt-d: Handle DID reservation errors when copying context tables
>   iommu/vt-d: Reserve scalable-mode DIDs from PASID entries during copy
>   iommu/vt-d: Use old domain parameter when attaching the blocking
>     domain
>   iommu/vt-d: Fix iopf refcount leak in nested attach
>   iommu/vt-d: Drop old iopf ref only after attach succeeds
> 
>  drivers/iommu/intel/iommu.h  |  17 +++-
>  drivers/iommu/intel/iommu.c  | 152 ++++++++++++++++++++++++++++++-----
>  drivers/iommu/intel/nested.c |   2 +
>  3 files changed, 149 insertions(+), 22 deletions(-)
> 

for entire series:

Reviewed-by: Kevin Tian <kevin.tian@intel.com>