From: Nicolin Chen <nicolinc@nvidia.com>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
"Joerg Roedel (AMD)" <joro@8bytes.org>,
Jean-Philippe Brucker <jpb@kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH RFC v3 1/3] iommu/arm-smmu-v3: Support shared SIDs in insert/remove_master
Date: Wed, 30 Sep 2026 11:11:51 -0700 [thread overview]
Message-ID: <ar1Q5y/xoa+Fcex7@nvidia.com> (raw)
In-Reply-To: <20260930-smmu-shared-sid-v3-1-8abe6c1b4c20@nxp.com>
On Wed, Sep 30, 2026 at 07:25:01PM +0800, Peng Fan (OSS) wrote:
> @@ -4115,7 +4128,10 @@ static int arm_smmu_insert_master(struct arm_smmu_device *smmu,
>
> new_stream->id = fwspec->ids[i];
> new_stream->master = master;
> + new_stream->ste_installed = false;
ste_installed is zero-ed.
> @@ -4136,23 +4152,29 @@ static int arm_smmu_insert_master(struct arm_smmu_device *smmu,
> existing = rb_find_add(&new_stream->node, &smmu->streams,
> arm_smmu_streams_cmp_node);
> if (existing) {
> - struct arm_smmu_master *existing_master =
> - rb_entry(existing, struct arm_smmu_stream, node)
> - ->master;
> + struct arm_smmu_stream *existing_stream =
> + rb_entry(existing, struct arm_smmu_stream, node);
>
> /* Bridged PCI devices may end up with duplicated IDs */
> - if (existing_master == master)
> + if (existing_stream->master == master)
> continue;
>
> - dev_warn(master->dev,
> - "Aliasing StreamID 0x%x (from %s) unsupported, expect DMA to be broken\n",
> - sid, dev_name(existing_master->dev));
> - ret = -ENODEV;
> - break;
> + if (master->num_streams != 1) {
> + dev_warn(master->dev,
> + "Shared StreamID 0x%x not supported for multi-SID masters\n",
> + sid);
> + ret = -ENODEV;
> + break;
> + }
> +
> + list_add_tail(&master->shared_masters_elm,
> + &existing_stream->shared_masters);
This version still uses the duplicated stream structures, not the
shared stream structure that I pointed out here:
https://lore.kernel.org/linux-iommu/arG6hmng3NddGEHm@nvidia.com/
?
This will have problems.
master_b->stream[0] --> new shared stream (SID=X) {shared_masters}
|
---------------- shared_masters_elm ----------|
v
master_a->stream[0] --> existing stream (SID=X) {shared_masters}
|
---------------- shared_masters_elm -----> {NULL}
First, the owner (master_a) doesn't add its shared_masters_elm to
any shared_masters list. This would fail the test on the owner:
!list_empty(&master->shared_masters_elm)
Then, ...
> @@ -4167,14 +4189,38 @@ static void arm_smmu_remove_master(struct arm_smmu_master *master)
> {
> int i;
> struct arm_smmu_device *smmu = master->smmu;
> - struct iommu_fwspec *fwspec = dev_iommu_fwspec_get(master->dev);
>
> if (!smmu || !master->streams)
> return;
>
> mutex_lock(&smmu->streams_mutex);
> - for (i = 0; i < fwspec->num_ids; i++)
> - rb_erase(&master->streams[i].node, &smmu->streams);
> + list_del_init(&master->shared_masters_elm);
> + for (i = 0; i < master->num_streams; i++) {
> + u32 sid = master->streams[i].id;
> + struct arm_smmu_stream *stream;
> +
> + if (i > 0 && master->streams[i - 1].id == sid)
> + continue;
> +
> + stream = arm_smmu_find_stream(smmu, sid);
> + if (!stream)
> + continue;
> +
> + if (stream->master != master)
> + continue;
> +
> + if (list_empty(&stream->shared_masters)) {
> + rb_erase(&stream->node, &smmu->streams);
> + } else {
> + struct arm_smmu_master *next;
> +
> + next = list_first_entry(&stream->shared_masters,
> + struct arm_smmu_master,
> + shared_masters_elm);
> + list_del_init(&next->shared_masters_elm);
> + stream->master = next;
> + }
> + }
> mutex_unlock(&smmu->streams_mutex);
>
> kfree(master->streams);
.. when the owner stream gets freed with the master_a, the shared
stream would UAF:
master_b->stream[0] --> new shared stream (SID=X) {shared_masters}
|
---------------- shared_masters_elm ----------|
v
{freed}
This should be changed to the model that I suggested in v2:
|---------------------------------------------------------|
| |
| |----------- shared_masters_elm --------| |
v | | |
master_a->stream[0] --| v |
|--> stream (SID=X) {shared_masters; master;}
master_b->stream[0] --| ^
| |
|----------- shared_masters_elm --------|
When any master is removed:
* Delink its shared_masters_elm
* Free the shared stream when its shared_masters is empty
If shared_masters isn't empty but the owner is removed:
* Give the ownership (stream->master pointer) to the next master
Nicolin
next prev parent reply other threads:[~2026-09-30 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 11:25 [PATCH RFC v3 0/3] iommu/arm-smmu-v3: Support shared Stream IDs Peng Fan (OSS)
2026-09-30 11:25 ` [PATCH RFC v3 1/3] iommu/arm-smmu-v3: Support shared SIDs in insert/remove_master Peng Fan (OSS)
2026-09-30 18:11 ` Nicolin Chen [this message]
2026-10-01 12:51 ` Peng Fan
2026-09-30 11:25 ` [PATCH RFC v3 2/3] iommu/arm-smmu-v3: Group aliasing devices into the same IOMMU group Peng Fan (OSS)
2026-09-30 11:25 ` [PATCH RFC v3 3/3] iommu/arm-smmu-v3: Wire up shared-SID STE ordering and feature gating Peng Fan (OSS)
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=ar1Q5y/xoa+Fcex7@nvidia.com \
--to=nicolinc@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=jpb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--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 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®