From: Vladimir Oltean <olteanv@gmail.com>
To: Sumera Priyadarsini <sylphrenadin@gmail.com>
Cc: andrew@lunn.ch, f.fainelli@gmail.com, netdev@vger.kernel.org,
sean.wang@mediatek.com, linux-kernel@vger.kernel.org,
vivien.didelot@gmail.com, Julia.Lawall@lip6.fr,
linux-mediatek@lists.infradead.org, matthias.bgg@gmail.com,
kuba@kernel.org, davem@davemloft.net,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3] net: dsa: Add of_node_put() before break and return statements
Date: Mon, 24 Aug 2020 16:35:15 +0300 [thread overview]
Message-ID: <20200824133515.j6ujfm2tl2hqjo5u@skbuf> (raw)
In-Reply-To: <20200823193054.29336-1-sylphrenadin@gmail.com>
On Mon, Aug 24, 2020 at 01:00:54AM +0530, Sumera Priyadarsini wrote:
> Every iteration of for_each_child_of_node() decrements
> the reference count of the previous node, however when control
> is transferred from the middle of the loop, as in the case of
> a return or break or goto, there is no decrement thus ultimately
> resulting in a memory leak.
>
> Fix a potential memory leak in mt7530.c by inserting of_node_put()
> before the break and return statements.
>
> Issue found with Coccinelle.
>
> ---
> Changes in v2:
> Add another of_node_put() in for_each_child_of_node() as pointed
> out by Andrew.
>
> Changes in v3:
> - Correct syntax errors
> - Modify commit message
>
> ---
>
> Signed-off-by: Sumera Priyadarsini <sylphrenadin@gmail.com>
>
> Signed-off-by: Sumera Priyadarsini <sylphrenadin@gmail.com>
> ---
If you need to resend anyway, can we please have a proper commit prefix?
A patch on mt7530.c shouldn't be "net: dsa: " but "net: dsa: mt7530: "
as "git log" will tell you. The difference is relevant because "net:
dsa: " typically refers to the generic code in net/dsa/.
> drivers/net/dsa/mt7530.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/dsa/mt7530.c b/drivers/net/dsa/mt7530.c
> index 8dcb8a49ab67..4b4701c69fe1 100644
> --- a/drivers/net/dsa/mt7530.c
> +++ b/drivers/net/dsa/mt7530.c
> @@ -1326,14 +1326,17 @@ mt7530_setup(struct dsa_switch *ds)
>
> if (phy_node->parent == priv->dev->of_node->parent) {
> ret = of_get_phy_mode(mac_np, &interface);
> - if (ret && ret != -ENODEV)
> + if (ret && ret != -ENODEV) {
> + of_node_put(mac_np);
> return ret;
> + }
> id = of_mdio_parse_addr(ds->dev, phy_node);
> if (id == 0)
> priv->p5_intf_sel = P5_INTF_SEL_PHY_P0;
> if (id == 4)
> priv->p5_intf_sel = P5_INTF_SEL_PHY_P4;
> }
> + of_node_put(mac_np);
> of_node_put(phy_node);
> break;
> }
> --
> 2.17.1
>
Thanks,
-Vladimir
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-08-24 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-23 19:30 [PATCH V3] net: dsa: Add of_node_put() before break and return statements Sumera Priyadarsini
2020-08-24 13:20 ` David Miller
2020-08-24 13:35 ` Vladimir Oltean [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=20200824133515.j6ujfm2tl2hqjo5u@skbuf \
--to=olteanv@gmail.com \
--cc=Julia.Lawall@lip6.fr \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sean.wang@mediatek.com \
--cc=sylphrenadin@gmail.com \
--cc=vivien.didelot@gmail.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