From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
bgolaszewski@baylibre.com, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] nvmem: core: add a missing of_node_put
Date: Fri, 23 Apr 2021 10:30:28 +0100 [thread overview]
Message-ID: <93e8b92c-8f4e-9990-ac4d-9688bbaaa6f6@linaro.org> (raw)
In-Reply-To: <2ebc18d9da622afe8681c18349b501a516253041.1618949512.git.christophe.jaillet@wanadoo.fr>
On 20/04/2021 21:12, Christophe JAILLET wrote:
> 'for_each_child_of_node' performs an of_node_get on each iteration, so a
> return from the middle of the loop requires an of_node_put.
>
> Fixes: e888d445ac33 ("nvmem: resolve cells from DT at registration time")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> drivers/nvmem/core.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
> index bca671ff4e54..4375e52ba6c2 100644
> --- a/drivers/nvmem/core.c
> +++ b/drivers/nvmem/core.c
> @@ -686,12 +686,15 @@ static int nvmem_add_cells_from_of(struct nvmem_device *nvmem)
> continue;
> if (len < 2 * sizeof(u32)) {
> dev_err(dev, "nvmem: invalid reg on %pOF\n", child);
> + of_node_put(child);
> return -EINVAL;
> }
>
> cell = kzalloc(sizeof(*cell), GFP_KERNEL);
> - if (!cell)
> + if (!cell) {
> + of_node_put(child);
> return -ENOMEM;
> + }
>
> cell->nvmem = nvmem;
> cell->np = of_node_get(child);
> @@ -717,6 +720,7 @@ static int nvmem_add_cells_from_of(struct nvmem_device *nvmem)
> kfree_const(cell->name);
> of_node_put(cell->np);
> kfree(cell);
> + of_node_put(child);
two of_node_put looks bit confusing to the reader, can you move the
cell->np = of_node_get(child); just before nvmem_cell_add(cell);
so that we can remove extra put.
Was this reported by some kind of static analysis tool?
--srini
> return -EINVAL;
> }
>
>
next prev parent reply other threads:[~2021-04-23 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 20:12 Christophe JAILLET
2021-04-23 9:30 ` Srinivas Kandagatla [this message]
2021-04-23 10:17 ` Christophe JAILLET
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=93e8b92c-8f4e-9990-ac4d-9688bbaaa6f6@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=bgolaszewski@baylibre.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.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®