All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Christian Engelmayer <cengelma@gmx.at>
Cc: olof@lixom.net, gwendal@chromium.org, wfrichar@chromium.org,
	smbarber@chromium.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: cros_ec: Fix possible leak in led_rgb_store()
Date: Thu, 23 Jul 2015 16:19:19 +0100	[thread overview]
Message-ID: <20150723151919.GM3436@x1> (raw)
In-Reply-To: <1437334982-3388-1-git-send-email-cengelma@gmx.at>

On Sun, 19 Jul 2015, Christian Engelmayer wrote:

> Function led_rgb_store() contains some direct returns in error cases that
> leak the already allocated cros_ec_command message structure. Make sure
> that 'msg' is freed in all exit paths. Detected by Coverity CID 1309666.
> 
> Signed-off-by: Christian Engelmayer <cengelma@gmx.at>
> ---
> Compile tested only. Applies against linux-next.
> ---
>  drivers/platform/chrome/cros_ec_lightbar.c | 8 +++-----
>  1 file changed, 3 insertions(+), 5 deletions(-)

This is not an MFD patch.

> diff --git a/drivers/platform/chrome/cros_ec_lightbar.c b/drivers/platform/chrome/cros_ec_lightbar.c
> index 144e09df9b84..4e598c11e8a4 100644
> --- a/drivers/platform/chrome/cros_ec_lightbar.c
> +++ b/drivers/platform/chrome/cros_ec_lightbar.c
> @@ -252,7 +252,7 @@ static ssize_t led_rgb_store(struct device *dev, struct device_attribute *attr,
>  
>  		ret = sscanf(buf, "%i", &val[i++]);
>  		if (ret == 0)
> -			return -EINVAL;
> +			goto exit;
>  
>  		if (i == 4) {
>  			param = (struct ec_params_lightbar *)msg->data;
> @@ -268,17 +268,15 @@ static ssize_t led_rgb_store(struct device *dev, struct device_attribute *attr,
>  			if ((j++ % 4) == 0) {
>  				ret = lb_throttle();
>  				if (ret)
> -					return ret;
> +					goto exit;
>  			}
>  
>  			ret = cros_ec_cmd_xfer(ec->ec_dev, msg);
>  			if (ret < 0)
>  				goto exit;
>  
> -			if (msg->result != EC_RES_SUCCESS) {
> -				ret = -EINVAL;
> +			if (msg->result != EC_RES_SUCCESS)
>  				goto exit;
> -			}
>  
>  			i = 0;
>  			ok = 1;

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  parent reply	other threads:[~2015-07-23 15:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-19 19:43 [PATCH] mfd: cros_ec: Fix possible leak in led_rgb_store() Christian Engelmayer
2015-07-20 14:50 ` Gwendal Grignou
2015-07-20 20:57   ` Christian Engelmayer
2015-07-23 15:19 ` Lee Jones [this message]
2015-08-21 17:11 ` Olof Johansson

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=20150723151919.GM3436@x1 \
    --to=lee.jones@linaro.org \
    --cc=cengelma@gmx.at \
    --cc=gwendal@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=smbarber@chromium.org \
    --cc=wfrichar@chromium.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.