From: Robin Murphy <robin.murphy@arm.com>
To: Miaoqian Lin <linmq006@gmail.com>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Thierry Reding <treding@nvidia.com>,
Rob Herring <robh@kernel.org>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] iommu/of: Fix device node reference leak in of_iommu_get_resv_regions
Date: Tue, 28 Oct 2025 11:57:00 +0000 [thread overview]
Message-ID: <6c35e1e4-8267-4eba-a53e-04ff74e224a2@arm.com> (raw)
In-Reply-To: <20251028063601.71934-1-linmq006@gmail.com>
On 2025-10-28 6:36 am, Miaoqian Lin wrote:
> In of_iommu_get_resv_regions(), of_find_node_by_phandle() returns a device
> node with its reference count incremented. The caller is responsible for
> releasing this reference when the node is no longer needed.
>
> Add a call to of_node_put() to release the reference after the usage.
Just put the reference immediately after getting it - this inner usage
only happens if it's the same dev->of_node we're already using for the
outer iteration, so we don't need to bother holding an extra reference
as it can't suddenly disappear anyway (or even if it could, that's still
not *this* code's problem...)
Thanks,
Robin.
> Found via static analysis.
>
> Fixes: a5bf3cfce8cb ("iommu: Implement of_iommu_get_resv_regions()")
> Cc: stable@vger.kernel.org
> Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
> ---
> drivers/iommu/of_iommu.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/iommu/of_iommu.c b/drivers/iommu/of_iommu.c
> index 6b989a62def2..02448da8ff90 100644
> --- a/drivers/iommu/of_iommu.c
> +++ b/drivers/iommu/of_iommu.c
> @@ -256,6 +256,7 @@ void of_iommu_get_resv_regions(struct device *dev, struct list_head *list)
> maps = of_translate_dma_region(np, maps, &iova, &length);
> if (length == 0) {
> dev_warn(dev, "Cannot reserve IOVA region of 0 size\n");
> + of_node_put(np);
> continue;
> }
> type = iommu_resv_region_get_type(dev, &phys, iova, length);
> @@ -265,6 +266,7 @@ void of_iommu_get_resv_regions(struct device *dev, struct list_head *list)
> if (region)
> list_add_tail(®ion->list, list);
> }
> + of_node_put(np);
> }
> }
> #endif
next prev parent reply other threads:[~2025-10-28 11:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 6:36 [PATCH] iommu/of: Fix device node reference leak in of_iommu_get_resv_regions Miaoqian Lin
2025-10-28 11:57 ` Robin Murphy [this message]
2025-10-28 13:05 ` Markus Elfring
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=6c35e1e4-8267-4eba-a53e-04ff74e224a2@arm.com \
--to=robin.murphy@arm.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=linmq006@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=treding@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox