From: William McVicker <willmcvicker@google.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: joro@8bytes.org, will@kernel.org,
Russell King <linux@armlinux.org.uk>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] amba: Fix driver_managed_dma check
Date: Wed, 30 Apr 2025 12:53:13 -0700 [thread overview]
Message-ID: <aBJ_qfy9cP_m5fSw@google.com> (raw)
In-Reply-To: <20250425133929.646493-1-robin.murphy@arm.com>
On 04/25/2025, Robin Murphy wrote:
> Since it's not currently safe to take device_lock() in the IOMMU probe
> path, that can race against really_probe() setting dev->driver before
> attempting to bind. The race itself isn't so bad, since we're only
> concerned with dereferencing dev->driver itself anyway, but sadly my
> attempt to implement the check with minimal churn leads to a kind of
> TOCTOU issue, where dev->driver becomes valid after to_amba_driver(NULL)
> is already computed, and thus the check fails to work as intended.
>
> Will and I both hit this with the platform bus, but the pattern here is
> the same, so fix it for correctness too.
Thanks!
Reviewed-by: Will McVicker <willmcvicker@google.com>
>
> Reported-by: Will McVicker <willmcvicker@google.com>
> Fixes: bcb81ac6ae3c ("iommu: Get DT/ACPI parsing into the proper probe path")
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
> drivers/amba/bus.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/amba/bus.c b/drivers/amba/bus.c
> index 71482d639a6d..84bc788663e6 100644
> --- a/drivers/amba/bus.c
> +++ b/drivers/amba/bus.c
> @@ -353,7 +353,7 @@ static void amba_shutdown(struct device *dev)
>
> static int amba_dma_configure(struct device *dev)
> {
> - struct amba_driver *drv = to_amba_driver(dev->driver);
> + const struct device_driver *drv = READ_ONCE(dev->driver);
> enum dev_dma_attr attr;
> int ret = 0;
>
> @@ -365,7 +365,7 @@ static int amba_dma_configure(struct device *dev)
> }
>
> /* @drv may not be valid when we're called from the IOMMU layer */
> - if (!ret && dev->driver && !drv->driver_managed_dma) {
> + if (!ret && drv && !to_amba_driver(drv)->driver_managed_dma) {
> ret = iommu_device_use_default_domain(dev);
> if (ret)
> arch_teardown_dma_ops(dev);
> --
> 2.39.2.101.g768bb238c484.dirty
>
prev parent reply other threads:[~2025-04-30 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 13:39 [PATCH] amba: Fix driver_managed_dma check Robin Murphy
2025-04-30 19:53 ` William McVicker [this message]
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=aBJ_qfy9cP_m5fSw@google.com \
--to=willmcvicker@google.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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 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.