linux-kernel - Re: [PATCH] clk: sunxi: Remove use of VLAIS

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 3 Mar 2016 10:07:07 -0800
From:	Chen-Yu Tsai <wens@...e.org>
To:	Stephen Boyd <sboyd@...eaurora.org>
Cc:	Michael Turquette <mturquette@...libre.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-clk <linux-clk@...r.kernel.org>,
	Chen-Yu Tsai <wens@...e.org>,
	Maxime Ripard <maxime.ripard@...e-electrons.com>
Subject: Re: [PATCH] clk: sunxi: Remove use of VLAIS

On Tue, Mar 1, 2016 at 4:20 PM, Stephen Boyd <sboyd@...eaurora.org> wrote:
> Using an array allocated on the stack may lead to stack overflows
> and other problems. Furthermore, VLAIS doesn't work well with
> LLVM compilers, so move the allocation to the heap and avoid the
> use of VLAIS here.
>
> Cc: Chen-Yu Tsai <wens@...e.org>
> Cc: Maxime Ripard <maxime.ripard@...e-electrons.com>
> Signed-off-by: Stephen Boyd <sboyd@...eaurora.org>
> ---
>  drivers/clk/sunxi/clk-sun8i-mbus.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/clk/sunxi/clk-sun8i-mbus.c b/drivers/clk/sunxi/clk-sun8i-mbus.c
> index 3aaa9cbef791..8e7128e69823 100644
> --- a/drivers/clk/sunxi/clk-sun8i-mbus.c
> +++ b/drivers/clk/sunxi/clk-sun8i-mbus.c
> @@ -33,7 +33,7 @@ static DEFINE_SPINLOCK(sun8i_a23_mbus_lock);
>  static void __init sun8i_a23_mbus_setup(struct device_node *node)
>  {
>         int num_parents = of_clk_get_parent_count(node);
> -       const char *parents[num_parents];
> +       const char **parents;
>         const char *clk_name = node->name;
>         struct resource res;
>         struct clk_divider *div;
> @@ -43,10 +43,14 @@ static void __init sun8i_a23_mbus_setup(struct device_node *node)
>         void __iomem *reg;
>         int err;
>
> +       parents = kcalloc(num_parents, sizeof(*parents), GFP_KERNEL);
> +       if (!parents)
> +               return;
> +
>         reg = of_io_request_and_map(node, 0, of_node_full_name(node));
>         if (!reg) {
>                 pr_err("Could not get registers for sun8i-mbus-clk\n");
> -               return;
> +               goto err_free_parents;
>         }
>
>         div = kzalloc(sizeof(*div), GFP_KERNEL);
> @@ -107,6 +111,8 @@ err_free_div:
>         kfree(div);
>  err_unmap:
>         iounmap(reg);
> +err_free_parents:
> +       kfree(parents);

AFAIK the CCF makes a deep copy of parents, so you should
always free it? I specifically checked it before using
VLAIS here.

ChenYu

>         of_address_to_resource(node, 0, &res);
>         release_mem_region(res.start, resource_size(&res));
>  }
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> a Linux Foundation Collaborative Project
>