All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Stephen Boyd <sboyd@codeaurora.org>,
	Mike Turquette <mturquette@linaro.org>,
	Lee Jones <lee@kernel.org>,
	Bryan Huntsman <bryanh@codeaurora.org>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Ralf Baechle <ralf@linux-mips.org>,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Tomeu Vizoso <tomeu.vizoso@collabora.com>
Subject: Re: [PATCH v1] clkdev: change prototype of clk_register_clkdev()
Date: Wed, 04 Feb 2015 18:03:55 +0200	[thread overview]
Message-ID: <1423065835.31903.424.camel@linux.intel.com> (raw)
In-Reply-To: <20150204155054.GK18758@lahna.fi.intel.com>

On Wed, 2015-02-04 at 17:50 +0200, Mika Westerberg wrote:
> On Tue, Feb 03, 2015 at 08:18:54PM +0200, Andy Shevchenko wrote:
> > Since clk_register_clkdev() is exported for modules the caller should get a
> > pointer to the allocated resources. Otherwise the memory leak is guaranteed on
> > the ->remove() stage.
> > 
> > Cc: Tomeu Vizoso <tomeu.vizoso@collabora.com>
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> 
> One comment, see below. Nothing major so feel free to add,
> 
> Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>

Thanks for review!

Though still wait for others to comment and test if possible.

By the way, I have to add that we have one unpublished (yet) user of
this. So, we are testing this internally on x86. Just to note that the
user is a module which might be unloaded. That's why important to
release the acquired resources.

> 
> > ---
> >  arch/arm/mach-msm/clock-pcom.c         |  9 +++++----
> >  arch/arm/mach-vexpress/spc.c           |  5 ++++-
> >  arch/mips/ath79/clock.c                |  6 +++---
> >  drivers/clk/clk-bcm2835.c              | 12 +++++++-----
> >  drivers/clk/clk-max-gen.c              |  9 ++++-----
> >  drivers/clk/clk-xgene.c                |  6 +++---
> >  drivers/clk/clkdev.c                   | 14 +++++++++-----
> >  drivers/clk/samsung/clk-pll.c          | 13 ++++++++-----
> >  drivers/clk/samsung/clk-s3c2410-dclk.c | 19 +++++++++---------
> >  drivers/clk/samsung/clk.c              | 35 +++++++++++++++++++---------------
> >  include/linux/clkdev.h                 |  2 +-
> >  11 files changed, 74 insertions(+), 56 deletions(-)
> 
> ...
> 
> > index 6e5c504..e07b1e2 100644
> > --- a/drivers/clk/clkdev.c
> > +++ b/drivers/clk/clkdev.c
> > @@ -307,29 +307,33 @@ EXPORT_SYMBOL(clkdev_drop);
> >   * clkdev.
> >   *
> >   * To make things easier for mass registration, we detect error clks
> > - * from a previous clk_register() call, and return the error code for
> > + * from a previous clk_register() call, and return the error pointer for
> >   * those.  This is to permit this function to be called immediately
> >   * after clk_register().
> > + *
> > + * Return:
> > + * pointer to the allocated struct clk_lookup on success, or error pointer
> > + * otherwise.
> 
> This should probably say how these resources are supposed to be
> released.

Agree. I would add this in v2.

-- 
Andy Shevchenko <andriy.shevchenko@intel.com>
Intel Finland Oy


  reply	other threads:[~2015-02-04 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-03 18:18 [PATCH v1] clkdev: prevent potential memory leak when used in modules Andy Shevchenko
2015-02-03 18:18 ` [PATCH v1] clkdev: change prototype of clk_register_clkdev() Andy Shevchenko
2015-02-04 15:50   ` Mika Westerberg
2015-02-04 16:03     ` Andy Shevchenko [this message]
2015-02-04 23:18   ` 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=1423065835.31903.424.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bryanh@codeaurora.org \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=mturquette@linaro.org \
    --cc=ralf@linux-mips.org \
    --cc=s.nawrocki@samsung.com \
    --cc=sboyd@codeaurora.org \
    --cc=tomeu.vizoso@collabora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.