All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: will@kernel.org, robin.murphy@arm.com, joro@8bytes.org,
	jsnitsel@redhat.com, kevin.tian@intel.com, praan@google.com,
	zhukeqian1@huawei.com, Jonathan.Cameron@huawei.com,
	jean-philippe@linaro.org, eric.auger@redhat.com,
	linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iommu/arm-smmu-v3: Fix iommu_device_probe bug due to duplicated stream ids
Date: Tue, 15 Apr 2025 10:24:01 -0300	[thread overview]
Message-ID: <20250415132401.GC517881@nvidia.com> (raw)
In-Reply-To: <20250412180658.439499-1-nicolinc@nvidia.com>

On Sat, Apr 12, 2025 at 11:06:58AM -0700, Nicolin Chen wrote:
> ASPEED VGA card has two built-in devices:
>  0008:06:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 06)
>  0008:07:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 52)
> 
> Since SMMU driver had been already expecting a potential duplicated Stream
> ID in arm_smmu_install_ste_for_dev(), change the arm_smmu_insert_master()
> routine to ignore a duplicated ID from the fwspec->sids array as well.
> 
> Note: this has been failing the iommu_device_probe() since 2021, although a
> recent iommu commit in v6.15-rc1 that moves iommu_device_probe() started to
> fail the SMMU driver probe. Since nobody has cared about DMA Alias support,
> leave that as it was but fix the fundamental iommu_device_probe() breakage.
> 
> Fixes: cdf315f907d4 ("iommu/arm-smmu-v3: Maintain a SID->device structure")
> Cc: stable@vger.kernel.org
> Suggested-by: Jason Gunthorpe <jgg@nvidia.com>
> Signed-off-by: Nicolin Chen <nicolinc@nvidia.com>
> ---
>  drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 19 +++++++++++++++----
>  1 file changed, 15 insertions(+), 4 deletions(-)

Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>

This should go to rc as it has become urgent with the probe
reorder. Use [PATCH rc] to idicate this..

Jason


  reply	other threads:[~2025-04-15 13:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-12 18:06 [PATCH] iommu/arm-smmu-v3: Fix iommu_device_probe bug due to duplicated stream ids Nicolin Chen
2025-04-15 13:24 ` Jason Gunthorpe [this message]
2025-04-15 18:52   ` Nicolin Chen

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=20250415132401.GC517881@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=eric.auger@redhat.com \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.org \
    --cc=joro@8bytes.org \
    --cc=jsnitsel@redhat.com \
    --cc=kevin.tian@intel.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolinc@nvidia.com \
    --cc=praan@google.com \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.org \
    --cc=zhukeqian1@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 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.