linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Chen-Yu Tsai <wens@csie.org>,
	Michael Turquette <mturquette@baylibre.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-clk <linux-clk@vger.kernel.org>
Subject: Re: [PATCH] clk: sunxi: Remove use of VLAIS
Date: Tue, 8 Mar 2016 23:13:20 +0100	[thread overview]
Message-ID: <20160308221320.GI8418@lukather> (raw)
In-Reply-To: <20160304171841.GF24999@codeaurora.org>

[-- Attachment #1: Type: text/plain, Size: 1643 bytes --]

On Fri, Mar 04, 2016 at 09:18:41AM -0800, Stephen Boyd wrote:
> On 03/04, Maxime Ripard wrote:
> > On Thu, Mar 03, 2016 at 11:16:04AM -0800, Stephen Boyd wrote:
> > > From: Stephen Boyd <sboyd@codeaurora.org>
> > > Subject: [PATCH] clk: sunxi: Remove use of VLAIS
> > 
> > VLAIS?
> 
> Hmm I guess it's just VLA, so llvm won't break. I'll reword
> commit text.
> 
> > 
> > > @@ -107,6 +112,8 @@ err_free_div:
> > >  	kfree(div);
> > >  err_unmap:
> > >  	iounmap(reg);
> > > +err_free_parents:
> > > +	kfree(parents);
> > >  	of_address_to_resource(node, 0, &res);
> > >  	release_mem_region(res.start, resource_size(&res));
> > 
> > The error path is wrong here, if you jump here from a failing call to
> > of_io_request_and_map, you'll end up releasing a memory region which
> > is not requested.
> > 
> 
> Oh right. Let's hope third time is the last.
> 
> ---8<---
> From: Stephen Boyd <sboyd@codeaurora.org>
> Subject: [PATCH] clk: sunxi: Remove use of variable length array
> 
> Using an array allocated on the stack may lead to stack overflows
> and other problems so let's move the allocation to the heap
> instead. This silences the following checker warning as well.
> 
> drivers/clk/sunxi/clk-sun8i-mbus.c:36:29: warning: Variable length array is used.
> 
> Cc: Chen-Yu Tsai <wens@csie.org>
> Cc: Maxime Ripard <maxime.ripard@free-electrons.com>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>

Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>

Thanks!
Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-03-08 22:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 19:48 [GIT PULL] arm: Allwinner clocks changes for 4.6 Maxime Ripard
2016-03-02  0:20 ` [PATCH] clk: sunxi: Remove use of VLAIS Stephen Boyd
2016-03-03 18:07   ` Chen-Yu Tsai
2016-03-03 19:16     ` Stephen Boyd
2016-03-04 15:27       ` Maxime Ripard
2016-03-04 17:18         ` Stephen Boyd
2016-03-08 22:13           ` Maxime Ripard [this message]
2016-03-15 22:16             ` Stephen Boyd
2016-03-16  8:51               ` Mason
2016-03-16 20:30                 ` Stephen Boyd
2016-03-16 20:44                   ` Mason
2016-03-18 17:47                   ` Maxime Ripard
2016-03-08 12:26   ` Mason
2016-03-02  1:46 ` [GIT PULL] arm: Allwinner clocks changes for 4.6 Stephen Boyd

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=20160308221320.GI8418@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@codeaurora.org \
    --cc=wens@csie.org \
    /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).