All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javier@osg.samsung.com>
To: Mark Brown <broonie@kernel.org>
Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Liam Girdwood <lgirdwood@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] regulator: core: Fix memory leak in regulator_resolve_supply()
Date: Wed, 15 Jul 2015 17:56:57 +0200	[thread overview]
Message-ID: <55A682C9.7040906@osg.samsung.com> (raw)
In-Reply-To: <20150715155254.GR11162@sirena.org.uk>

Hello Mark,

On 07/15/2015 05:52 PM, Mark Brown wrote:
> On Wed, Jul 15, 2015 at 02:46:25PM +0200, Javier Martinez Canillas wrote:
>> On 07/15/2015 01:27 PM, Mark Brown wrote:
> 
>>> using _regulator_get() I think.  A separate, rarely used, path is likely
>>> to have this sort of issue.
> 
>> Exactly, do you agree then that a try_module_get() is missing in set_supply()?
> 
>> It is OK if I add that in the same patch in v2 or do you prefer that to be
>> in a separate patch?
> 
> A separate patch would be better, or even better would be something that
> just replaces everything there with use of the same code path as _get()
> (thanks for volunteering!) but just adding the try_module_get() is fine
> for now.
> 

I already posted a v2 of the series which adds a try_module_get() as a
separate patch but I'll add to my TODO list at factoring out both code
paths as a follow-up.

Best regards,
-- 
Javier Martinez Canillas
Open Source Group
Samsung Research America

      reply	other threads:[~2015-07-15 15:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 14:21 [PATCH] regulator: core: Fix memory leak in regulator_resolve_supply() Javier Martinez Canillas
2015-07-15  8:01 ` Krzysztof Kozlowski
2015-07-15  8:38   ` Javier Martinez Canillas
2015-07-15 11:27     ` Mark Brown
2015-07-15 12:46       ` Javier Martinez Canillas
2015-07-15 15:52         ` Mark Brown
2015-07-15 15:56           ` Javier Martinez Canillas [this message]

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=55A682C9.7040906@osg.samsung.com \
    --to=javier@osg.samsung.com \
    --cc=broonie@kernel.org \
    --cc=k.kozlowski@samsung.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.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 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.