All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Christian Engelmayer <cengelma@gmx.at>,
	Milo Kim <milo.kim@ti.com>,
	linux-pwm@vger.kernel.org
Subject: Re: [PATCH] pwm: lp3943: Fix potential memory leak during request
Date: Mon, 27 Jan 2014 13:51:52 +0100	[thread overview]
Message-ID: <20140127125151.GA7058@ulmo.nvidia.com> (raw)
In-Reply-To: <20140127095803.GC14478@lee--X1>

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

On Mon, Jan 27, 2014 at 09:58:03AM +0000, Lee Jones wrote:
> On Fri, 24 Jan 2014, Thierry Reding wrote:
> 
> > On Thu, Jan 23, 2014 at 10:32:20PM +0100, Christian Engelmayer wrote:
> > > Fix a memory leak in the lp3943_pwm_request_map() error handling path.
> > > Make sure already allocated pwm map memory is freed correctly.
> > > Detected by Coverity: CID 1162829.
> > > 
> > > Signed-off-by: Christian Engelmayer <cengelma@gmx.at>
> > > ---
> > >  drivers/pwm/pwm-lp3943.c | 4 +++-
> > >  1 file changed, 3 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/pwm/pwm-lp3943.c b/drivers/pwm/pwm-lp3943.c
> > > index 8a843a0..a40b9c3 100644
> > > --- a/drivers/pwm/pwm-lp3943.c
> > > +++ b/drivers/pwm/pwm-lp3943.c
> > > @@ -52,8 +52,10 @@ lp3943_pwm_request_map(struct lp3943_pwm *lp3943_pwm, int hwpwm)
> > >  		offset = pwm_map->output[i];
> > >  
> > >  		/* Return an error if the pin is already assigned */
> > > -		if (test_and_set_bit(offset, &lp3943->pin_used))
> > > +		if (test_and_set_bit(offset, &lp3943->pin_used)) {
> > > +			kfree(pwm_map);
> > >  			return ERR_PTR(-EBUSY);
> > > +		}
> > >  	}
> > >  
> > >  	return pwm_map;
> > 
> > Lee, since you took this driver via the MFD tree, would you mind picking
> > up this fix as well?
> 
> Everything I have is now in Mainline.
> 
> It's best for you to apply it now I think?

Sure, I could do that after -rc1 is released. It's somewhat problematic
because I can't really create a tree that's based on yours before -rc1.
After -rc1 it shouldn't be a problem and this also isn't all that
critical, so sending off another pull request to Linus after -rc1 is
probably what I'll do.

Thierry

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

  reply	other threads:[~2014-01-27 12:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23 21:32 [PATCH] pwm: lp3943: Fix potential memory leak during request Christian Engelmayer
2014-01-23 22:47 ` Milo Kim
2014-01-24 16:23 ` Thierry Reding
2014-01-27  9:58   ` Lee Jones
2014-01-27 12:51     ` Thierry Reding [this message]
2014-02-26 15:09 ` Thierry Reding

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=20140127125151.GA7058@ulmo.nvidia.com \
    --to=thierry.reding@gmail.com \
    --cc=cengelma@gmx.at \
    --cc=lee.jones@linaro.org \
    --cc=linux-pwm@vger.kernel.org \
    --cc=milo.kim@ti.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.