From: Mark Brown <broonie@debian.org>
To: Rob Herring <robh+dt@kernel.org>
Cc: Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Luca Di Stefano <luca.distefano@linaro.org>,
993612@bugs.debian.org, stable@kernel.org
Subject: Re: [PATCH] of/address: Return an error when no valid dma-ranges are found
Date: Fri, 27 Jan 2023 19:05:47 +0000 [thread overview]
Message-ID: <Y9Qgi2osVrP/qcAM@sirena.org.uk> (raw)
In-Reply-To: <CAL_JsqLPUKS2+8-sShADSYxAgxjP3mh=TcZPszFeYbMTiPvjYQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
On Fri, Jan 27, 2023 at 12:37:35PM -0600, Rob Herring wrote:
> Looks to me like we are leaking 'r' with this change.
Oh, probably now that you mention it. Usually the OF code keeps
track of more things than I expect...
> Wouldn't this change work:
> diff --git a/drivers/of/address.c b/drivers/of/address.c
> index c34ac33b7338..f43311f01c32 100644
> --- a/drivers/of/address.c
> +++ b/drivers/of/address.c
> @@ -968,6 +968,11 @@ int of_dma_get_range(struct device_node *np,
> const struct bus_dma_region **map)
> for_each_of_range(&parser, &range)
> num_ranges++;
>
> + if (!num_ranges) {
> + ret = -EINVAL;
> + goto out;
> + }
> +
Not as-is, there is a range counted by that first loop but it's
then rejected by the check in the second loop for cpu_addr ==
OF_BAD_ADDR. We'd need to add a similar check in the first loop.
It should work otherwise though and avoids doing the allocation
in this case.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-01-27 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 16:26 [PATCH] of/address: Return an error when no valid dma-ranges are found Mark Brown
2023-01-27 18:37 ` Rob Herring
2023-01-27 19:05 ` Mark Brown [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=Y9Qgi2osVrP/qcAM@sirena.org.uk \
--to=broonie@debian.org \
--cc=993612@bugs.debian.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.distefano@linaro.org \
--cc=robh+dt@kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).