From: Stephan Gerhold <stephan@gerhold.net>
To: Robin Murphy <robin.murphy@arm.com>
Cc: linux-arm-msm@vger.kernel.org, joro@8bytes.org,
iommu@lists.linux-foundation.org, robdclark@gmail.com,
Naresh Kamboju <naresh.kamboju@linaro.org>,
linux-arm-kernel@lists.infradead.org,
Brian Masney <masneyb@onstation.org>
Subject: Re: [PATCH] iommu/qcom: Fix bogus detach logic
Date: Tue, 18 Feb 2020 20:05:16 +0100 [thread overview]
Message-ID: <20200218190516.GA19773@gerhold.net> (raw)
In-Reply-To: <be92829c6e5467634b109add002351e6cf9e18d2.1582049382.git.robin.murphy@arm.com>
On Tue, Feb 18, 2020 at 06:12:41PM +0000, Robin Murphy wrote:
> Currently, the implementation of qcom_iommu_domain_free() is guaranteed
> to do one of two things: WARN() and leak everything, or dereference NULL
> and crash. That alone is terrible, but in fact the whole idea of trying
> to track the liveness of a domain via the qcom_domain->iommu pointer as
> a sanity check is full of fundamentally flawed assumptions. Make things
> robust and actually functional by not trying to be quite so clever.
>
> Reported-by: Brian Masney <masneyb@onstation.org>
> Tested-by: Brian Masney <masneyb@onstation.org>
> Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
> Fixes: 0ae349a0f33f ("iommu/qcom: Add qcom_iommu")
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
This fixes the warning reported by Naresh Kamboju [1] for me. Thank you!
Tested-by: Stephan Gerhold <stephan@gerhold.net>
[1]: https://lore.kernel.org/linux-arm-msm/CA+G9fYtScOpkLvx=__gP903uJ2v87RwZgkAuL6RpF9_DTDs9Zw@mail.gmail.com/
> ---
> drivers/iommu/qcom_iommu.c | 28 ++++++++++++----------------
> 1 file changed, 12 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/iommu/qcom_iommu.c b/drivers/iommu/qcom_iommu.c
> index 39759db4f003..4328da0b0a9f 100644
> --- a/drivers/iommu/qcom_iommu.c
> +++ b/drivers/iommu/qcom_iommu.c
> @@ -344,21 +344,19 @@ static void qcom_iommu_domain_free(struct iommu_domain *domain)
> {
> struct qcom_iommu_domain *qcom_domain = to_qcom_iommu_domain(domain);
>
> - if (WARN_ON(qcom_domain->iommu)) /* forgot to detach? */
> - return;
> -
> iommu_put_dma_cookie(domain);
>
> - /* NOTE: unmap can be called after client device is powered off,
> - * for example, with GPUs or anything involving dma-buf. So we
> - * cannot rely on the device_link. Make sure the IOMMU is on to
> - * avoid unclocked accesses in the TLB inv path:
> - */
> - pm_runtime_get_sync(qcom_domain->iommu->dev);
> -
> - free_io_pgtable_ops(qcom_domain->pgtbl_ops);
> -
> - pm_runtime_put_sync(qcom_domain->iommu->dev);
> + if (qcom_domain->iommu) {
> + /*
> + * NOTE: unmap can be called after client device is powered
> + * off, for example, with GPUs or anything involving dma-buf.
> + * So we cannot rely on the device_link. Make sure the IOMMU
> + * is on to avoid unclocked accesses in the TLB inv path:
> + */
> + pm_runtime_get_sync(qcom_domain->iommu->dev);
> + free_io_pgtable_ops(qcom_domain->pgtbl_ops);
> + pm_runtime_put_sync(qcom_domain->iommu->dev);
> + }
>
> kfree(qcom_domain);
> }
> @@ -404,7 +402,7 @@ static void qcom_iommu_detach_dev(struct iommu_domain *domain, struct device *de
> struct qcom_iommu_domain *qcom_domain = to_qcom_iommu_domain(domain);
> unsigned i;
>
> - if (!qcom_domain->iommu)
> + if (WARN_ON(!qcom_domain->iommu))
> return;
>
> pm_runtime_get_sync(qcom_iommu->dev);
> @@ -417,8 +415,6 @@ static void qcom_iommu_detach_dev(struct iommu_domain *domain, struct device *de
> ctx->domain = NULL;
> }
> pm_runtime_put_sync(qcom_iommu->dev);
> -
> - qcom_domain->iommu = NULL;
> }
>
> static int qcom_iommu_map(struct iommu_domain *domain, unsigned long iova,
> --
> 2.23.0.dirty
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-18 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 18:12 [PATCH] iommu/qcom: Fix bogus detach logic Robin Murphy
2020-02-18 19:05 ` Stephan Gerhold [this message]
2020-02-19 10:56 ` Joerg Roedel
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=20200218190516.GA19773@gerhold.net \
--to=stephan@gerhold.net \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=masneyb@onstation.org \
--cc=naresh.kamboju@linaro.org \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.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;
as well as URLs for NNTP newsgroup(s).