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 1/7] mfd: 88pm860x: Fix possible NULL pointer dereference on i2c_new_dummy error
Date: Tue, 11 Feb 2014 12:21:46 +0000 [thread overview]
Message-ID: <20140211122146.GP32042@lee--X1> (raw)
In-Reply-To: <1392113015-11180-1-git-send-email-k.kozlowski@samsung.com>
On Tue, 11 Feb 2014, Krzysztof Kozlowski wrote:
> During probe the driver allocates dummy I2C device for companion chip
> with i2c_new_dummy() but it does not check the return value of this call.
>
> 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 regmap_init_i2c().
>
> If i2c_new_dummy() fails for companion device, fail also the probe for
> main MFD driver.
>
> Signed-off-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Cc: stable@vger.kernel.org
> ---
> drivers/mfd/88pm860x-core.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/mfd/88pm860x-core.c b/drivers/mfd/88pm860x-core.c
> index c9b1f6422941..e456be9a7c67 100644
> --- a/drivers/mfd/88pm860x-core.c
> +++ b/drivers/mfd/88pm860x-core.c
> @@ -1179,6 +1179,11 @@ static int pm860x_probe(struct i2c_client *client,
> chip->companion_addr = pdata->companion_addr;
> chip->companion = i2c_new_dummy(chip->client->adapter,
> chip->companion_addr);
> + if (!chip->companion) {
> + dev_err(&client->dev,
> + "Failed to allocate I2C companion device\n");
> + return -ENODEV;
> + }
> chip->regmap_companion = regmap_init_i2c(chip->companion,
> &pm860x_regmap_config);
> if (IS_ERR(chip->regmap_companion)) {
Applied, thanks.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2014-02-11 12:21 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
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 ` Lee Jones [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=20140211122146.GP32042@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).