linux-kernel - Re: [PATCH V2] clk: renesas: Fix memory leak of 'cpg'

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:   Wed, 13 Apr 2022 13:23:54 +0200
From:   Geert Uytterhoeven <geert@...ux-m68k.org>
To:     白浩文 <baihaowen@...zu.com>
Cc:     Michael Turquette <mturquette@...libre.com>,
        Stephen Boyd <sboyd@...nel.org>,
        Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
        linux-clk <linux-clk@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V2] clk: renesas: Fix memory leak of 'cpg'

Hi Haowen,

On Wed, Apr 13, 2022 at 12:44 PM 白浩文 <baihaowen@...zu.com> wrote:
> But this function __init r8a73a4_cpg_clocks_init will auto free by system after boot

The memory containing the code for the function
r8a73a4_cpg_clocks_init() will indeed be freed.  But the data
structures allocated and prepared by the function will continue to
exist afterwards.

> On Wed, Apr 13, 2022 at 11:24 AM baihaowen <baihaowen@...zu.com> wrote:
> > 在 4/13/22 4:41 PM, Geert Uytterhoeven 写道:
> > > On Wed, Apr 13, 2022 at 10:30 AM Haowen Bai <baihaowen@...zu.com> wrote:
> > >> Fix this issue by freeing the cpg when exiting the function in the
> > >> error/normal path.
> > >>
> > >> Signed-off-by: Haowen Bai <baihaowen@...zu.com>

> > >> --- a/drivers/clk/renesas/clk-r8a73a4.c
> > >> +++ b/drivers/clk/renesas/clk-r8a73a4.c
> > >> @@ -215,7 +215,7 @@ static void __init r8a73a4_cpg_clocks_init(struct device_node *np)
> > >>
> > >>         cpg->reg = of_iomap(np, 0);
> > >>         if (WARN_ON(cpg->reg == NULL))
> > >> -               return;
> > >> +               goto out_free_cpg;
> > > Note that this is a fatal error, i.e. no chance the system will survive this,
> > > so cleaning up is moot.
> > >
> > >>         for (i = 0; i < num_clks; ++i) {
> > >>                 const char *name;
> > >> @@ -233,6 +233,9 @@ static void __init r8a73a4_cpg_clocks_init(struct device_node *np)
> > >>         }
> > >>
> > >>         of_clk_add_provider(np, of_clk_src_onecell_get, &cpg->data);
> > >> +out_free_cpg:
> > >> +       kfree(cpg);
> > >> +       kfree(clks);
> > > Both cpg and clks are still used after returning from this function,
> > > through the registered clocks and clock provider.
> > >
> > >>  }
> > >>  CLK_OF_DECLARE(r8a73a4_cpg_clks, "renesas,r8a73a4-cpg-clocks",
> > >>                r8a73a4_cpg_clocks_init);
> > > NAKed-by: Geert Uytterhoeven <geert+renesas@...der.be>
>
> > Could you show me how and when cpg & clks free ?
>
> They are never freed, as they stay in-use for the lifetime of the system.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds