From: "Suthikulpanit, Suravee" <suravee.suthikulpanit@amd.com>
To: "guanghuifeng@linux.alibaba.com" <guanghuifeng@linux.alibaba.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
joro@8bytes.org, jgg@nvidia.com
Cc: yi.l.liu@intel.com, kevin.tian@intel.com, nicolinc@nvidia.com,
vasant.hegde@amd.com, jon.grimm@amd.com, santosh.shukla@amd.com,
Sairaj.K@amd.com, jay.chen@amd.com, wvw@google.com,
wnliu@google.com, dantuluris@google.com, chriscli@google.com,
kpsingh@google.com, alejandro.j.jimenez@oracle.com,
joao.m.martins@oracle.com
Subject: Re: [PATCH 24/24] iommu/amd: Relocate vIOMMU translate-device-id on PCI reserve
Date: Thu, 3 Sep 2026 10:56:29 +0700 [thread overview]
Message-ID: <6ecb2ec1-974b-4ef3-aae3-ace4aa90baf8@amd.com> (raw)
In-Reply-To: <6576c2cf-fe35-4c64-ab19-0120494d7e42@linux.alibaba.com>
On 8/19/2026 4:42 PM, guanghuifeng@linux.alibaba.com wrote:
>
> 在 2026/7/27 21:29, Suravee Suthikulpanit 写道:
>> When PCI attach reserves a BDF already allocated to a vIOMMU, relocate
>> that vIOMMU to a newly allocated translate-device-id before marking the
>> BDF reserved for the device. Reprogram translation DTE and VFctrl under
>> trans_devid_lock; roll back the pool on failure.
>>
>> Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
>> ---
>> drivers/iommu/amd/trans_devid.c | 116 +++++++++++++++++++++++++++++++-
>> 1 file changed, 115 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/iommu/amd/trans_devid.c b/drivers/iommu/amd/
>> trans_devid.c
>> index 9d7d93c5dcdb..6fb1ba3c9444 100644
>> --- a/drivers/iommu/amd/trans_devid.c
>> +++ b/drivers/iommu/amd/trans_devid.c
>> @@ -82,16 +82,120 @@ void amd_iommu_pci_seg_trans_devid_fini(struct
>>
>> ....
>>
>> +static int trans_devid_relocate(struct amd_iommu_pci_seg *pci_seg,
>> u16 from_id,
>> + struct amd_iommu_viommu *aviommu)
>> +{
>> + u16 new_id;
>> + int ret;
>> +
>> + mutex_lock(&aviommu->trans_devid_lock);
>> +
>> + mutex_lock(&pci_seg->trans_devid_mutex);
>> + if (trans_devid_xa_owner(xa_load(&pci_seg->trans_devid_xa,
>> from_id)) !=
>> + aviommu) {
>> + ret = -ENOENT;
>> + goto unlock_seg;
>> + }
>> +
>> + if (aviommu->trans_devid != from_id) {
>> + ret = -EINVAL;
>> + goto unlock_seg;
>> + }
>> +
>> + new_id = trans_devid_find_free_locked(pci_seg);
>> + if (new_id < 0) {
>> + ret = new_id;
>> + goto unlock_seg;
>> + }
>
>
> This has a type-truncation bug. trans_devid_find_free_locked() returns
> int and signals failure with -ENOSPC. Assigning it to a u16 truncates
> -ENOSPC (-28) to 65508 (0xFFDC), and the subsequent "if (new_id < 0)"
> is always false for an unsigned u16. On pool exhaustion the code would
> proceed to install and program a DTE with the bogus ID 65508. Please
> change new_id to int:
>
> int new_id;
>
I'll fix in v5.
Thanks,
Suravee
next prev parent reply other threads:[~2026-09-03 3:56 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 13:28 [PATCH v4 00/24] iommu/amd: Introduce AMD Hardware-accelerated Virtualized IOMMU (vIOMMU) Support Suravee Suthikulpanit
2026-07-27 13:28 ` [PATCH 01/24] iommu/amd: Make amd_iommu_completion_wait() non-static Suravee Suthikulpanit
2026-08-05 17:01 ` Vasant Hegde
2026-09-01 7:56 ` Suthikulpanit, Suravee
2026-07-27 13:28 ` [PATCH 02/24] iommu/amd: Introduce vIOMMU-specific events and event Suravee Suthikulpanit
2026-08-10 7:12 ` Vasant Hegde
2026-09-01 8:28 ` Suthikulpanit, Suravee
2026-08-19 8:17 ` guanghuifeng
2026-09-01 14:21 ` Suthikulpanit, Suravee
2026-07-27 13:28 ` [PATCH 03/24] iommu/amd: Detect and initialize AMD vIOMMU feature Suravee Suthikulpanit
2026-08-10 8:13 ` Vasant Hegde
2026-09-01 16:32 ` Suthikulpanit, Suravee
2026-07-27 13:28 ` [PATCH 04/24] iommu/amd: Introduce IOMMUFD vIOMMU support for AMD Suravee Suthikulpanit
2026-08-24 17:24 ` Jason Gunthorpe
2026-07-27 13:28 ` [PATCH 05/24] iommu/amd: Allocate Guest IDs for IOMMUFD vIOMMU instances Suravee Suthikulpanit
2026-08-10 9:21 ` Vasant Hegde
2026-09-02 7:49 ` Suthikulpanit, Suravee
2026-08-24 17:24 ` Jason Gunthorpe
2026-09-02 7:50 ` Suthikulpanit, Suravee
2026-07-27 13:28 ` [PATCH 06/24] iommu/amd: Map vIOMMU VF and VF Control MMIO BARs Suravee Suthikulpanit
2026-08-10 10:00 ` Vasant Hegde
2026-09-02 12:16 ` Suthikulpanit, Suravee
2026-08-19 13:18 ` guanghuifeng
2026-09-02 12:16 ` Suthikulpanit, Suravee
2026-07-27 13:28 ` [PATCH 07/24] iommu/amd: Add support for AMD vIOMMU VF MMIO region Suravee Suthikulpanit
2026-08-10 10:49 ` Vasant Hegde
2026-08-24 17:24 ` Jason Gunthorpe
2026-07-27 13:28 ` [PATCH 08/24] iommu/amd: Introduce Reset vMMIO Command Suravee Suthikulpanit
2026-08-19 8:34 ` guanghuifeng
2026-09-02 22:33 ` Suthikulpanit, Suravee
2026-07-27 13:28 ` [PATCH 09/24] iommu/amd: Introduce and map vIOMMU private IPA region Suravee Suthikulpanit
2026-08-24 17:24 ` Jason Gunthorpe
2026-07-27 13:28 ` [PATCH 10/24] iommu/amd: Pass iommu to device_flush_dte() Suravee Suthikulpanit
2026-08-10 11:07 ` Vasant Hegde
2026-08-24 17:24 ` Jason Gunthorpe
2026-07-27 13:29 ` [PATCH 11/24] iommu/amd: Export amd_iommu_alloc_dev_data() helper Suravee Suthikulpanit
2026-08-24 17:24 ` Jason Gunthorpe
2026-07-27 13:29 ` [PATCH 12/24] iommu/amd: Pass iommu and devid to amd_iommu_make_clear_dte() Suravee Suthikulpanit
2026-08-24 17:24 ` Jason Gunthorpe
2026-07-27 13:29 ` [PATCH 13/24] iommu/amd: Assign IOMMU Private Address domain to IOMMU Suravee Suthikulpanit
2026-08-24 17:24 ` Jason Gunthorpe
2026-07-27 13:29 ` [PATCH 14/24] iommu/amd: Add per-VM private IPA alloc/map helpers Suravee Suthikulpanit
2026-08-24 17:24 ` Jason Gunthorpe
2026-07-27 13:29 ` [PATCH 15/24] iommu/amd: Add helper functions to manage DevID / DomID mapping tables Suravee Suthikulpanit
2026-08-19 13:30 ` guanghuifeng
2026-09-03 0:41 ` Suthikulpanit, Suravee
2026-07-27 13:29 ` [PATCH 16/24] iommu/amd: Introduce IOMMUFD vDevice support for AMD Suravee Suthikulpanit
2026-08-19 13:34 ` guanghuifeng
2026-09-03 2:41 ` Suthikulpanit, Suravee
2026-08-24 17:24 ` Jason Gunthorpe
2026-07-27 13:29 ` [PATCH 17/24] iommu/amd: Introduce helper function for updating domain ID mapping table Suravee Suthikulpanit
2026-08-19 10:45 ` guanghuifeng
2026-09-03 3:26 ` Suthikulpanit, Suravee
2026-07-27 13:29 ` [PATCH 18/24] iommu/amd: Introduce helper function for updating device " Suravee Suthikulpanit
2026-08-10 15:17 ` Vasant Hegde
2026-09-03 3:19 ` Suthikulpanit, Suravee
2026-08-19 10:26 ` guanghuifeng
2026-07-27 13:29 ` [PATCH 19/24] iommu/amd: Add per-segment translate device ID pool Suravee Suthikulpanit
2026-07-27 13:29 ` [PATCH 20/24] iommu/amd: Reserve translate-device-id for PCI requestor aliases Suravee Suthikulpanit
2026-07-27 13:29 ` [PATCH 21/24] iommu/amd: Add translation DTE and VFctrl TransDevID helpers Suravee Suthikulpanit
2026-07-27 13:29 ` [PATCH 22/24] iommu/amd: Add translate-device-id alloc/free with vIOMMU owner Suravee Suthikulpanit
2026-07-27 13:29 ` [PATCH 23/24] iommu/amd: Assign per-vIOMMU translate device ID Suravee Suthikulpanit
2026-08-19 10:18 ` guanghuifeng
2026-07-27 13:29 ` [PATCH 24/24] iommu/amd: Relocate vIOMMU translate-device-id on PCI reserve Suravee Suthikulpanit
2026-08-19 9:42 ` guanghuifeng
2026-09-03 3:56 ` Suthikulpanit, Suravee [this message]
2026-08-11 7:18 ` [PATCH v4 00/24] iommu/amd: Introduce AMD Hardware-accelerated Virtualized IOMMU (vIOMMU) Support Tian, Kevin
2026-08-24 17:24 ` Jason Gunthorpe
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=6ecb2ec1-974b-4ef3-aae3-ace4aa90baf8@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=Sairaj.K@amd.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=chriscli@google.com \
--cc=dantuluris@google.com \
--cc=guanghuifeng@linux.alibaba.com \
--cc=iommu@lists.linux.dev \
--cc=jay.chen@amd.com \
--cc=jgg@nvidia.com \
--cc=joao.m.martins@oracle.com \
--cc=jon.grimm@amd.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kpsingh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=santosh.shukla@amd.com \
--cc=vasant.hegde@amd.com \
--cc=wnliu@google.com \
--cc=wvw@google.com \
--cc=yi.l.liu@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
all inboxes | Powered by JetHome®