From: Nicolin Chen <nicolinc@nvidia.com>
To: Qinxin Xia <xiaqinxin@huawei.com>
Cc: <will@kernel.org>, <robin.murphy@arm.com>, <jpb@kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<wangzhou1@hisilicon.com>, <prime.zeng@hisilicon.com>,
<fanghao11@huawei.com>, <jonathan.cameron@huawei.com>,
<linuxarm@huawei.com>
Subject: Re: [RFC PATCH 5/5] iommu/arm-smmu-v3: Add Context Descriptor display to debugfs
Date: Fri, 13 Mar 2026 14:04:10 -0700 [thread overview]
Message-ID: <abR7ys1LYRhJ8Hn6@Asurada-Nvidia> (raw)
In-Reply-To: <20260313104351.3502293-6-xiaqinxin@huawei.com>
On Fri, Mar 13, 2026 at 06:43:51PM +0800, Qinxin Xia wrote:
> * Directory Structure:
> * /sys/kernel/debug/iommu/arm_smmu_v3/
> * └── smmu0/
> @@ -35,6 +42,8 @@
> * └── stream_table
> * └── 0000:01:00.0:0/ # PCI device with Stream ID 0
> * ├── ste # Stream Table Entry
> + * └── context_descriptors/
> + * └── all # All Context Descriptors
I wonder if we should do per-RID/PASID v.s. all. Otherwise, cd_dir
seems unnecessary, as it could be a file instead?
> +/**
> + * smmu_debug_dump_cd() - Dump Context Descriptor details to seq_file
> + * @seq: seq_file to write to
> + * @dev: device associated with the CD
> + * @ssid: Substream ID
> + */
> +static void smmu_debug_dump_cd(struct seq_file *seq, struct device *dev, u32 ssid)
> +{
> + struct arm_smmu_master *master = dev_iommu_priv_get(dev);
> + struct arm_smmu_cd *cd;
> + u64 data;
> + int i;
> +
> + if (!master) {
> + seq_puts(seq, "No master data\n");
> + return;
> + }
> +
> + cd = arm_smmu_get_cd_ptr(master, ssid);
> + if (!cd) {
> + seq_printf(seq, "CD not available for SSID %u\n", ssid);
> + return;
> + }
master->cd_table can be free-ed. We could hit UAF in a race. This
very likely needs arm_smmu_asid_lock.
> + seq_printf(seq, "CD for Substream ID %u:\n", ssid);
> +
> + /* CD 0 */
> + data = le64_to_cpu(cd->data[0]);
> + seq_printf(seq, " Valid: %s\n", data & CTXDESC_CD_0_V ? "Yes" : "No");
> + seq_printf(seq, " T0SZ: 0x%llx\n", data & CTXDESC_CD_0_TCR_T0SZ);
> + seq_printf(seq, " EPD0: %s\n", data & CTXDESC_CD_0_TCR_EPD0 ? "Yes" : "No");
> + seq_printf(seq, " EPD1: %s\n", data & CTXDESC_CD_0_TCR_EPD1 ? "Yes" : "No");
All these are unnecessary if V=0? Maybe the per-SSID output should
depend on V=1 at all. Same might apply to STE.
> +/* All CDs debugfs file operations */
> +static int smmu_debugfs_all_cds_show(struct seq_file *seq, void *v)
> +{
> + struct device *dev = seq->private;
> +
> + smmu_debug_dump_all_cds(seq, dev);
> + return 0;
Just unwrap the smmu_debug_dump_all_cds().
Nicolin
next prev parent reply other threads:[~2026-03-13 21:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 10:43 [RFC PATCH 0/5] Add debugfs support for ARM SMMUv3 Qinxin Xia
2026-03-13 10:43 ` [RFC PATCH 1/5] iommu/arm-smmu-v3: Add basic debugfs framework Qinxin Xia
2026-03-13 19:58 ` Nicolin Chen
2026-03-16 15:14 ` Qinxin Xia
2026-03-13 10:43 ` [RFC PATCH 2/5] iommu/arm-smmu-v3: Add register display to debugfs Qinxin Xia
2026-03-13 20:20 ` Nicolin Chen
2026-03-16 15:22 ` Qinxin Xia
2026-03-16 15:19 ` Robin Murphy
2026-03-16 15:35 ` Qinxin Xia
2026-03-16 16:26 ` Robin Murphy
2026-03-17 1:44 ` Qinxin Xia
2026-03-13 10:43 ` [RFC PATCH 3/5] iommu/arm-smmu-v3: Add Stream Table Entry " Qinxin Xia
2026-03-13 20:19 ` Nicolin Chen
2026-03-16 15:43 ` Qinxin Xia
2026-03-13 10:43 ` [RFC PATCH 4/5] iommu/arm-smmu-v3: Add stream table directory structure " Qinxin Xia
2026-03-13 20:44 ` Nicolin Chen
2026-03-16 14:57 ` Qinxin Xia
2026-03-16 16:01 ` Robin Murphy
2026-03-17 2:04 ` Qinxin Xia
2026-03-13 10:43 ` [RFC PATCH 5/5] iommu/arm-smmu-v3: Add Context Descriptor display " Qinxin Xia
2026-03-13 21:04 ` Nicolin Chen [this message]
2026-03-16 15:12 ` Qinxin Xia
2026-03-16 15:42 ` Robin Murphy
2026-03-17 2:14 ` Qinxin Xia
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=abR7ys1LYRhJ8Hn6@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=fanghao11@huawei.com \
--cc=iommu@lists.linux.dev \
--cc=jonathan.cameron@huawei.com \
--cc=jpb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linuxarm@huawei.com \
--cc=prime.zeng@hisilicon.com \
--cc=robin.murphy@arm.com \
--cc=wangzhou1@hisilicon.com \
--cc=will@kernel.org \
--cc=xiaqinxin@huawei.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