From: Rob Herring <robh@kernel.org>
To: frowand.list@gmail.com
Cc: Slawomir Stepien <slawomir.stepien@nokia.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Herring <robh+dt@kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
linux-kernel@vger.kernel.org, Slawomir Stepien <sst@poczta.fm>,
pantelis.antoniou@konsulko.com, devicetree@vger.kernel.org,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH v2 3/3] of: overlay: do not free changeset when of_overlay_apply returns error
Date: Mon, 2 May 2022 19:59:07 -0500 [thread overview]
Message-ID: <YnB+W6u5dL44vEBL@robh.at.kernel.org> (raw)
In-Reply-To: <20220502181742.1402826-4-frowand.list@gmail.com>
On Mon, 02 May 2022 13:17:42 -0500, frowand.list@gmail.com wrote:
> From: Frank Rowand <frank.rowand@sony.com>
>
> New unittests for overlay notifiers reveal a memory leak in
> of_overlay_apply() when a notifier returns an error for action
> OF_OVERLAY_POST_APPLY. The pr_err() message is:
>
> OF: ERROR: memory leak, expected refcount 1 instead of 3,
> of_node_get()/of_node_put() unbalanced - destroy cset entry: attach
> overlay node /testcase-data/overlay-node/test-bus/test-unittest17
>
> Change the error path to no longer call free_overlay_changeset(),
> and document that the caller of of_overlay_fdt_apply() may choose
> to remove the overlay.
>
> Update the unittest that triggered the error to expect the changed
> return values and to call of_overlay_remove().
>
> Signed-off-by: Frank Rowand <frank.rowand@sony.com>
> ---
> Changes since version 1:
> - patch 1/1 v1 did not apply on Rob's dt/next branch, rebase on top of
> 5f756a2eaa44 of: overlay: do not break notify on NOTIFY_{OK|STOP}
>
> Output of the new overlay notifier unittests, as filtered by
> scripts/dtc/of_unittest_expect:
>
> ### dt-test ### pass of_unittest_overlay_notify():2825
> ok OF: overlay: overlay changeset pre-apply notifier error -16, target: /testcase-data/overlay-node/test-bus
> ### dt-test ### pass of_unittest_overlay_notify():2846
> ### dt-test ### pass of_unittest_overlay_notify():2851
> ok OF: overlay: overlay changeset post-apply notifier error -17, target: /testcase-data/overlay-node/test-bus
> ### dt-test ### pass of_unittest_overlay_notify():2857
> ### dt-test ### pass of_unittest_overlay_notify():2862
> ### dt-test ### pass of_unittest_overlay_notify():2866
> ### dt-test ### pass of_unittest_overlay_notify():2872
> ### dt-test ### pass of_unittest_overlay_notify():2875
> ok OF: overlay: overlay changeset pre-remove notifier error -18, target: /testcase-data/overlay-node/test-bus
> ### dt-test ### pass of_unittest_overlay_notify():2886
> ### dt-test ### pass of_unittest_overlay_notify():2894
> ### dt-test ### pass of_unittest_overlay_notify():2898
> ### dt-test ### pass of_unittest_overlay_notify():2901
> ok OF: overlay: overlay changeset post-remove notifier error -19, target: /testcase-data/overlay-node/test-bus
> ### dt-test ### pass of_unittest_overlay_notify():2908
> ### dt-test ### pass of_unittest_overlay_notify():2915
> ### dt-test ### pass of_unittest_overlay_notify():2920
> ### dt-test ### pass of_unittest_overlay_notify():2932
>
>
> drivers/of/overlay.c | 29 ++++++++++++++++++++++++++---
> drivers/of/unittest.c | 10 ++++++++--
> 2 files changed, 34 insertions(+), 5 deletions(-)
>
Applied, thanks!
prev parent reply other threads:[~2022-05-03 1:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 18:17 [PATCH v2 0/3] of: overlay: unittest: fix overlay notify error, add overlay notifier tests, fix bug revealed by new unittests frowand.list
2022-05-02 18:17 ` [PATCH v2 1/3] of: overlay: add entry to of_overlay_action_name[] frowand.list
2022-05-03 0:56 ` Rob Herring
2022-05-02 18:17 ` [PATCH v2 2/3] of: overlay: unittest: add tests for overlay notifiers frowand.list
2022-05-03 0:58 ` Rob Herring
2022-05-02 18:17 ` [PATCH v2 3/3] of: overlay: do not free changeset when of_overlay_apply returns error frowand.list
2022-05-03 0:59 ` Rob Herring [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=YnB+W6u5dL44vEBL@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=geert+renesas@glider.be \
--cc=jan.kiszka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pantelis.antoniou@konsulko.com \
--cc=robh+dt@kernel.org \
--cc=slawomir.stepien@nokia.com \
--cc=sst@poczta.fm \
/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