From: Pratyush Brahma <quic_pbrahma@quicinc.com>
To: Robin Murphy <robin.murphy@arm.com>, Will Deacon <will@kernel.org>
Cc: <catalin.marinas@arm.com>, <kernel-team@android.com>,
<joro@8bytes.org>, <jgg@ziepe.ca>, <jsnitsel@redhat.com>,
<robdclark@chromium.org>, <quic_c_gdjako@quicinc.com>,
<dmitry.baryshkov@linaro.org>,
<linux-arm-kernel@lists.infradead.org>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <quic_charante@quicinc.com>,
<stable@vger.kernel.org>, Prakash Gupta <quic_guptap@quicinc.com>
Subject: Re: [PATCH v2] iommu/arm-smmu: Defer probe of clients after smmu device bound
Date: Wed, 20 Nov 2024 00:40:10 +0530 [thread overview]
Message-ID: <1d3dcd91-d246-4db3-9717-9edfe405f431@quicinc.com> (raw)
In-Reply-To: <0952ca36-c5d9-462a-ab7b-b97154c56919@arm.com>
On 11/7/2024 8:31 PM, Robin Murphy wrote:
> On 29/10/2024 4:15 pm, Will Deacon wrote:
>> On Fri, 04 Oct 2024 14:34:28 +0530, Pratyush Brahma wrote:
>>> Null pointer dereference occurs due to a race between smmu
>>> driver probe and client driver probe, when of_dma_configure()
>>> for client is called after the iommu_device_register() for smmu driver
>>> probe has executed but before the driver_bound() for smmu driver
>>> has been called.
>>>
>>> Following is how the race occurs:
>>>
>>> [...]
>>
>> Applied to will (for-joerg/arm-smmu/updates), thanks!
>>
>> [1/1] iommu/arm-smmu: Defer probe of clients after smmu device bound
>> https://git.kernel.org/will/c/229e6ee43d2a
>
> I've finally got to the point of proving to myself that this isn't the
> right fix, since once we do get __iommu_probe_device() working properly
> in the correct order, iommu_device_register() then runs into the same
> condition itself. Diff below should make this issue go away - I'll write
> up proper patches once I've tested it a little more.
>
> Thanks,
> Robin.
>
> ----->8-----
> diff --git a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> index 737c5b882355..b7dcb1494aa4 100644
> --- a/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> +++ b/drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c
> @@ -3171,8 +3171,8 @@ static struct platform_driver arm_smmu_driver;
> static
> struct arm_smmu_device *arm_smmu_get_by_fwnode(struct fwnode_handle
> *fwnode)
> {
> - struct device *dev =
> driver_find_device_by_fwnode(&arm_smmu_driver.driver,
> - fwnode);
> + struct device *dev =
> bus_find_device_by_fwnode(&platform_bus_type, fwnode);
> + put_device(dev);
> return dev ? dev_get_drvdata(dev) : NULL;
> }
> diff --git a/drivers/iommu/arm/arm-smmu/arm-smmu.c
> b/drivers/iommu/arm/arm-smmu/arm-smmu.c
> index 8321962b3714..aba315aa6848 100644
> --- a/drivers/iommu/arm/arm-smmu/arm-smmu.c
> +++ b/drivers/iommu/arm/arm-smmu/arm-smmu.c
> @@ -1411,8 +1411,8 @@ static bool arm_smmu_capable(struct device *dev,
> enum iommu_cap cap)
> static
> struct arm_smmu_device *arm_smmu_get_by_fwnode(struct fwnode_handle
> *fwnode)
> {
> - struct device *dev =
> driver_find_device_by_fwnode(&arm_smmu_driver.driver,
> - fwnode);
> + struct device *dev =
> bus_find_device_by_fwnode(&platform_bus_type, fwnode);
I think it would still follow this path:
bus_find_device_by_fwnode() -> bus_find_device() -> next_device()
next_device() would always return null until the driver is bound to the
device which
happens much later in really_probe() after the iommu_device_register()
would be called
even as per this patch. That way the race would still occur, wouldn't it?
Can you please help me understand what I may be missing here?
Are you saying that these additional patches are required along with the
fix I've
posted?
> +
> put_device(dev);
> return dev ? dev_get_drvdata(dev) : NULL;
> }
> @@ -2232,21 +2232,6 @@ static int arm_smmu_device_probe(struct
> platform_device *pdev)
> i, irq);
> }
>
> - err = iommu_device_sysfs_add(&smmu->iommu, smmu->dev, NULL,
> - "smmu.%pa", &smmu->ioaddr);
> - if (err) {
> - dev_err(dev, "Failed to register iommu in sysfs\n");
> - return err;
> - }
> -
> - err = iommu_device_register(&smmu->iommu, &arm_smmu_ops,
> - using_legacy_binding ? NULL : dev);
> - if (err) {
> - dev_err(dev, "Failed to register iommu\n");
> - iommu_device_sysfs_remove(&smmu->iommu);
> - return err;
> - }
> -
> platform_set_drvdata(pdev, smmu);
>
> /* Check for RMRs and install bypass SMRs if any */
> @@ -2255,6 +2240,18 @@ static int arm_smmu_device_probe(struct
> platform_device *pdev)
> arm_smmu_device_reset(smmu);
> arm_smmu_test_smr_masks(smmu);
>
> + err = iommu_device_sysfs_add(&smmu->iommu, smmu->dev, NULL,
> + "smmu.%pa", &smmu->ioaddr);
> + if (err)
> + return dev_err_probe(dev, err, "Failed to register iommu in
> sysfs\n");
> +
> + err = iommu_device_register(&smmu->iommu, &arm_smmu_ops,
> + using_legacy_binding ? NULL : dev);
> + if (err) {
> + iommu_device_sysfs_remove(&smmu->iommu);
> + return dev_err_probe(dev, err, "Failed to register iommu\n");
> + }
> +
> /*
> * We want to avoid touching dev->power.lock in fastpaths unless
> * it's really going to do something useful - pm_runtime_enabled()
--
Thanks and Regards
Pratyush Brahma
next prev parent reply other threads:[~2024-11-19 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 9:04 Pratyush Brahma
2024-10-15 13:31 ` Pratyush Brahma
2024-10-17 13:54 ` Robin Murphy
2024-10-27 15:36 ` Pratyush Brahma
2024-10-29 16:15 ` Will Deacon
2024-11-07 15:01 ` Robin Murphy
2024-11-19 19:10 ` Pratyush Brahma [this message]
2024-11-21 14:49 ` Robin Murphy
2024-11-21 21:05 ` Pratyush Brahma
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=1d3dcd91-d246-4db3-9717-9edfe405f431@quicinc.com \
--to=quic_pbrahma@quicinc.com \
--cc=catalin.marinas@arm.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=jsnitsel@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_c_gdjako@quicinc.com \
--cc=quic_charante@quicinc.com \
--cc=quic_guptap@quicinc.com \
--cc=robdclark@chromium.org \
--cc=robin.murphy@arm.com \
--cc=stable@vger.kernel.org \
--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®