All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Sangbeom Kim <sbkim73@samsung.com>,
	Samuel Ortiz <sameo@linux.intel.com>,
	linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Marek Szyprowski <m.szyprowski@samsung.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH 4/7] mfd: max77693: Fix possible NULL pointer dereference on i2c_new_dummy error
Date: Tue, 11 Feb 2014 12:22:49 +0000	[thread overview]
Message-ID: <20140211122249.GS32042@lee--X1> (raw)
In-Reply-To: <1392113015-11180-4-git-send-email-k.kozlowski@samsung.com>

On Tue, 11 Feb 2014, Krzysztof Kozlowski wrote:

> During probe the driver allocates dummy I2C devices for MUIC and haptic
> with i2c_new_dummy() but it does not check the return value of this
> calls.
> 
> In case of error (i2c_new_device(): memory allocation failure or I2C
> address cannot be used) this function returns NULL which is later used
> by devm_regmap_init_i2c() and i2c_unregister_device().
> 
> If i2c_new_dummy() fails for MUIC or haptic devices, fail also the probe
> for main MFD driver.
> 
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Cc: stable@vger.kernel.org
> ---
>  drivers/mfd/max77693.c |   12 +++++++++++-
>  1 file changed, 11 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/mfd/max77693.c b/drivers/mfd/max77693.c
> index e0859987ab6b..c5535f018466 100644
> --- a/drivers/mfd/max77693.c
> +++ b/drivers/mfd/max77693.c
> @@ -148,9 +148,18 @@ static int max77693_i2c_probe(struct i2c_client *i2c,
>  		dev_info(max77693->dev, "device ID: 0x%x\n", reg_data);
>  
>  	max77693->muic = i2c_new_dummy(i2c->adapter, I2C_ADDR_MUIC);
> +	if (!max77693->muic) {
> +		dev_err(max77693->dev, "Failed to allocate I2C device for MUIC\n");
> +		return -ENODEV;
> +	}
>  	i2c_set_clientdata(max77693->muic, max77693);
>  
>  	max77693->haptic = i2c_new_dummy(i2c->adapter, I2C_ADDR_HAPTIC);
> +	if (!max77693->haptic) {
> +		dev_err(max77693->dev, "Failed to allocate I2C device for Haptic\n");
> +		ret = -ENODEV;
> +		goto err_i2c_haptic;
> +	}
>  	i2c_set_clientdata(max77693->haptic, max77693);
>  
>  	/*
> @@ -184,8 +193,9 @@ err_mfd:
>  	max77693_irq_exit(max77693);
>  err_irq:
>  err_regmap_muic:
> -	i2c_unregister_device(max77693->muic);
>  	i2c_unregister_device(max77693->haptic);
> +err_i2c_haptic:
> +	i2c_unregister_device(max77693->muic);
>  	return ret;
>  }
>  

Applied, thanks.

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

  reply	other threads:[~2014-02-11 12:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 10:03 [PATCH 1/7] mfd: 88pm860x: Fix possible NULL pointer dereference on i2c_new_dummy error Krzysztof Kozlowski
2014-02-11 10:03 ` [PATCH 2/7] mfd: 88pm860x: Fix I2C device resource leak on regmap init fail Krzysztof Kozlowski
2014-02-11 12:22   ` Lee Jones
2014-02-11 10:03 ` [PATCH 3/7] mfd: max77686: Fix possible NULL pointer dereference on i2c_new_dummy error Krzysztof Kozlowski
2014-02-11 12:22   ` Lee Jones
2014-02-11 10:03 ` [PATCH 4/7] mfd: max77693: " Krzysztof Kozlowski
2014-02-11 12:22   ` Lee Jones [this message]
2014-02-11 10:03 ` [PATCH 5/7] mfd: max8925: " Krzysztof Kozlowski
2014-02-11 12:23   ` Lee Jones
2014-02-11 10:03 ` [PATCH 6/7] mfd: max8997: " Krzysztof Kozlowski
2014-02-11 12:23   ` Lee Jones
2014-02-11 10:03 ` [PATCH 7/7] mfd: max8998: " Krzysztof Kozlowski
2014-02-11 12:23   ` Lee Jones
2014-02-11 12:21 ` [PATCH 1/7] mfd: 88pm860x: " Lee Jones

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=20140211122249.GS32042@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=k.kozlowski@samsung.com \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=m.szyprowski@samsung.com \
    --cc=sameo@linux.intel.com \
    --cc=sbkim73@samsung.com \
    --cc=stable@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.