From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Marc Gonzalez <marc.w.gonzalez@free.fr>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Xidong Wang <wangxidong_97@163.com>,
Mans Rullgard <mans@mansr.com>,
Marek Vasut <marek.vasut@gmail.com>,
Richard Weinberger <richard@nod.at>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH 1/1] mtd:nand:fix memory leak
Date: Thu, 5 Apr 2018 11:54:48 +0200 [thread overview]
Message-ID: <20180405115448.36d2372f@bbrezillon> (raw)
In-Reply-To: <6ae95633-d82f-1294-c7c7-db59c00d1d4d@free.fr>
On Thu, 5 Apr 2018 11:12:11 +0200
Marc Gonzalez <marc.w.gonzalez@free.fr> wrote:
> On 04/04/2018 09:08, Boris Brezillon wrote:
>
> > On Wed, 4 Apr 2018 09:07:10 +0200
> > Boris Brezillon <boris.brezillon@bootlin.com> wrote:
> >
> >> On Wed, 4 Apr 2018 08:28:07 +0200
> >> Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> >>
> >>> Hi Xidong,
> >>>
> >>> As part of a reorganization in the NAND subsystem, you should now
> >>> prefix your commit title this way:
> >>>
> >>> mtd: rawnand: tango: fix memory leak
> >>>
> >>> Not sure if this patch is candidate to cc:stable?
> >>>
> >>> On Wed, 4 Apr 2018 11:05:51 +0800, Xidong Wang
> >>> <wangxidong_97@163.com> wrote:
> >>>
> >>>> In function tango_nand_probe(), the memory allocated by
> >>>> clk_get() is not released on the normal path and
> >>>> the error path that IS_ERR(nfc->chan) returns true.
> >>>
> >>> The fact that the error path returns true looks out of topic, can you
> >>> remove it? Just saying that you fix a memory leak is enough I guess.
> >>>
> >>>> This will result in a memory leak bug.
> >>>>
> >>>> Signed-off-by: Xidong Wang <wangxidong_97@163.com>
> >>>> ---
> >>>> drivers/mtd/nand/tango_nand.c | 5 ++++-
> >>>> 1 file changed, 4 insertions(+), 1 deletion(-)
> >>>>
> >>>> diff --git a/drivers/mtd/nand/tango_nand.c b/drivers/mtd/nand/tango_nand.c
> >>>> index c5bee00b..8083459 100644
> >>>> --- a/drivers/mtd/nand/tango_nand.c
> >>>> +++ b/drivers/mtd/nand/tango_nand.c
> >>>> @@ -648,12 +648,15 @@ static int tango_nand_probe(struct platform_device *pdev)
> >>>> return PTR_ERR(clk);
> >>>>
> >>>> nfc->chan = dma_request_chan(&pdev->dev, "rxtx");
> >>>> - if (IS_ERR(nfc->chan))
> >>>> + if (IS_ERR(nfc->chan)) {
> >>>> + clk_put(clk);
> >>>> return PTR_ERR(nfc->chan);
> >>>> + }
> >>>>
> >>>> platform_set_drvdata(pdev, nfc);
> >>>> nand_hw_control_init(&nfc->hw);
> >>>> nfc->freq_kHz = clk_get_rate(clk) / 1000;
> >>>> + clk_put(clk);
> >>>
> >>> If the clock is used only here, better do the frequency derivation
> >>> right after the clock_get(), and follow with a clk_put()? This way you
> >>> don't have to change the error path and 'related' actions remain
> >>> grouped.
> >>
> >> Hm, definitely not a good idea to release the reference you have on the
> >> clk if the driver depends on it. I recommend using devm_clk_get() to
> >> solve this leak.
> >
> > BTW, it's also weird that the driver does not prepare_enable the clk.
> > Marc, any comments?
>
> I was not aware that clk_get() allocated memory, and required clk_put()
> for cleanup. IIRC, I looked at Documentation/clk.txt
>
> On tango, clocks are configured by the boot loader. The existing clk driver
> provides only read access to various clocks -- except the CPU clock, which
> can be changed by tweaking a post-divider. Tweaking the PLLs requires much
> more complex code. The boot loader enables every clock, and Linux has no
> way to gate any of them.
Well, even if that's not supported today, it's always a good practice
to retain reference and prepare/enable clks your HW depends on. This
change should be harmless and when/if you someday decide to provide a
way to gate clks, it will work out of the box.
>
> In the nfc driver, all I needed was the system frequency, since the NFC is
> driven by the system clock (which can never be disabled).
>
> Thus, I wrote the naive (and apparently incorrect)
>
> clk = clk_get(&pdev->dev, NULL);
> nfc->freq_kHz = clk_get_rate(clk) / 1000;
>
>
> I suppose the following patch would fix the memory leak, and
> matches what Miquèl suggested.
>
> Regards.
>
>
> diff --git a/drivers/mtd/nand/tango_nand.c b/drivers/mtd/nand/tango_nand.c
> index c5bee00b7f5e..fba162af333f 100644
> --- a/drivers/mtd/nand/tango_nand.c
> +++ b/drivers/mtd/nand/tango_nand.c
> @@ -646,6 +646,8 @@ static int tango_nand_probe(struct platform_device *pdev)
> clk = clk_get(&pdev->dev, NULL);
Why not using devm_clk_get() and be done with it?
> if (IS_ERR(clk))
> return PTR_ERR(clk);
> + nfc->freq_kHz = clk_get_rate(clk) / 1000;
> + clk_put(clk);
And that's where I disagree. Clearly, you're not following one of the
clk consumer's rule: "when you need a clk, keep a reference to it and
enable it before you start using the HW".
>
> nfc->chan = dma_request_chan(&pdev->dev, "rxtx");
> if (IS_ERR(nfc->chan))
> @@ -653,7 +655,6 @@ static int tango_nand_probe(struct platform_device *pdev)
>
> platform_set_drvdata(pdev, nfc);
> nand_hw_control_init(&nfc->hw);
> - nfc->freq_kHz = clk_get_rate(clk) / 1000;
>
> for_each_child_of_node(pdev->dev.of_node, np) {
> err = chip_init(&pdev->dev, np);
next prev parent reply other threads:[~2018-04-05 9:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 3:05 [PATCH 1/1] mtd:nand:fix memory leak Xidong Wang
2018-04-04 6:28 ` Miquel Raynal
2018-04-04 7:07 ` Boris Brezillon
2018-04-04 7:08 ` Boris Brezillon
2018-04-05 9:12 ` Marc Gonzalez
2018-04-05 9:44 ` Miquel Raynal
2018-04-05 11:04 ` Boris Brezillon
2018-04-05 9:54 ` Boris Brezillon [this message]
2018-04-05 11:26 ` Marc Gonzalez
2018-04-05 11:47 ` Boris Brezillon
2018-04-05 12:00 ` Marc Gonzalez
2018-04-05 12:57 ` [PATCH v2] mtd: rawnand: tango: Fix struct clk " Marc Gonzalez
2018-04-05 14:22 ` Miquel Raynal
2018-04-24 15:50 ` Boris Brezillon
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=20180405115448.36d2372f@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mans@mansr.com \
--cc=marc.w.gonzalez@free.fr \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=wangxidong_97@163.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;
as well as URLs for NNTP newsgroup(s).