From: "Enrico Weigelt, metux IT consult" <lkml@metux.net>
To: Jacek Anaszewski <jacek.anaszewski@gmail.com>, Kangjie Lu <kjlu@umn.edu>
Cc: pakki001@umn.edu, Riku Voipio <riku.voipio@iki.fi>,
Pavel Machek <pavel@ucw.cz>,
linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds: fix a potential NULL pointer dereference
Date: Mon, 11 Mar 2019 11:09:08 +0100 [thread overview]
Message-ID: <32c84850-85e8-e063-b104-220afe0554f8@metux.net> (raw)
In-Reply-To: <8c616b91-8f0d-f53b-af10-4d768063c5a0@gmail.com>
On 10.03.19 21:27, Jacek Anaszewski wrote:
> Hi Kangjie,
>
> Thank you for the patch.
>
> On 3/9/19 7:04 AM, Kangjie Lu wrote:
>> In case of_match_device cannot find a match, the fixes returns
>> -EINVAL to avoid NULL pointer dereference.
>>
>> Signed-off-by: Kangjie Lu <kjlu@umn.edu>
>> ---
>> drivers/leds/leds-pca9532.c | 8 ++++++--
>> 1 file changed, 6 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/leds/leds-pca9532.c b/drivers/leds/leds-pca9532.c
>> index 7fea18b0c15d..4b0335591728 100644
>> --- a/drivers/leds/leds-pca9532.c
>> +++ b/drivers/leds/leds-pca9532.c
>> @@ -513,6 +513,7 @@ static int pca9532_probe(struct i2c_client *client,
>> const struct i2c_device_id *id)
>> {
>> int devid;
>> + const struct of_device_id *of_id;
Looks like an indention mismatch that might call for the
Great White Handkerchief ;-)
--mtx
--
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@metux.net -- +49-151-27565287
next prev parent reply other threads:[~2019-03-11 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 6:04 Kangjie Lu
2019-03-10 20:27 ` Jacek Anaszewski
2019-03-11 10:09 ` Enrico Weigelt, metux IT consult [this message]
2019-03-31 9:06 ` Geert Uytterhoeven
2019-03-31 10:52 ` Jacek Anaszewski
2019-03-31 11:01 ` Jacek Anaszewski
2019-04-01 7:08 ` Geert Uytterhoeven
2019-04-02 18:48 ` Jacek Anaszewski
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=32c84850-85e8-e063-b104-220afe0554f8@metux.net \
--to=lkml@metux.net \
--cc=jacek.anaszewski@gmail.com \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pakki001@umn.edu \
--cc=pavel@ucw.cz \
--cc=riku.voipio@iki.fi \
/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
all inboxes | Powered by JetHome®