From: "Pali Rohár" <pali.rohar@gmail.com>
To: Colin King <colin.king@canonical.com>
Cc: Sebastian Reichel <sre@kernel.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] power: supply: bq2415x: check for NULL acpi_id to avoid null pointer dereference
Date: Sat, 21 Jan 2017 01:02:20 +0100 [thread overview]
Message-ID: <20170121000220.GI32502@pali> (raw)
In-Reply-To: <20170120132506.20514-1-colin.king@canonical.com>
On Friday 20 January 2017 13:25:06 Colin King wrote:
> From: Colin Ian King <colin.king@canonical.com>
>
> acpi_match_device can potentially return NULL, so it is prudent to
> check if acpi_id is null before it is dereferenced. Add a check
> and an error message to indicate the failure.
>
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
> ---
> drivers/power/supply/bq2415x_charger.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/power/supply/bq2415x_charger.c b/drivers/power/supply/bq2415x_charger.c
> index 73e2f0b..c4770a9 100644
> --- a/drivers/power/supply/bq2415x_charger.c
> +++ b/drivers/power/supply/bq2415x_charger.c
> @@ -1569,6 +1569,11 @@ static int bq2415x_probe(struct i2c_client *client,
> acpi_id =
> acpi_match_device(client->dev.driver->acpi_match_table,
> &client->dev);
> + if (!acpi_id) {
> + dev_err(&client->dev, "failed to match device name\n");
> + ret = -ENODEV;
> + goto error_1;
> + }
> name = kasprintf(GFP_KERNEL, "%s-%d", acpi_id->id, num);
> }
> if (!name) {
Looks good! Add my Reviewed-by.
--
Pali Rohár
pali.rohar@gmail.com
next prev parent reply other threads:[~2017-01-21 0:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 13:25 [PATCH] power: supply: bq2415x: check for NULL acpi_id to avoid null pointer dereference Colin King
2017-01-21 0:02 ` Pali Rohár [this message]
2017-01-29 15:17 ` Sebastian Reichel
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=20170121000220.GI32502@pali \
--to=pali.rohar@gmail.com \
--cc=colin.king@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@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).