From: Mukesh Ojha <mojha@codeaurora.org>
To: Lee Jones <lee.jones@linaro.org>, Kangjie Lu <kjlu@umn.edu>
Cc: pakki001@umn.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: fix a potential NULL pointer dereference
Date: Mon, 25 Mar 2019 14:43:25 +0530 [thread overview]
Message-ID: <be967424-090f-d388-4530-47a9a817db1f@codeaurora.org> (raw)
In-Reply-To: <20190325075608.GY4731@dell>
On 3/25/2019 1:26 PM, Lee Jones wrote:
> On Fri, 22 Mar 2019, Kangjie Lu wrote:
>
>> Hi Lee Jones,
>>
>> Can you review this patch?
> Don't poke.
>
> I have a very long list of reviews on my TODO. Poking only surfaces
> your patch to the top of my Inbox, and since I review patches in
> reverse chronological order, it puts the review to the back of the
> queue.
>
>>> On Mar 9, 2019, at 2:04 AM, Kangjie Lu <kjlu@umn.edu> wrote:
>>>
>>> In case devm_kzalloc fails, the fix does NULL check and returns
>>> -ENOMEM upon failure so as to avoid NULL pointer dereference.
>>>
>>> Signed-off-by: Kangjie Lu <kjlu@umn.edu>
>>> ---
>>> drivers/mfd/sm501.c | 3 +++
>>> 1 file changed, 3 insertions(+)
>>>
>>> diff --git a/drivers/mfd/sm501.c b/drivers/mfd/sm501.c
>>> index a530972c5a7e..e0173bf4b0dc 100644
>>> --- a/drivers/mfd/sm501.c
>>> +++ b/drivers/mfd/sm501.c
>>> @@ -1145,6 +1145,9 @@ static int sm501_register_gpio_i2c_instance(struct sm501_devdata *sm,
>>> lookup = devm_kzalloc(&pdev->dev,
>>> sizeof(*lookup) + 3 * sizeof(struct gpiod_lookup),
>>> GFP_KERNEL);
>>> + if (!lookup)
>>> + return -ENOMEM;
Seems you are using quite old codebase.
This patch is already there ..
https://elixir.bootlin.com/linux/v5.1-rc2/source/drivers/mfd/sm501.c#L1147
commit ae7b8eda27b3( mfd: sm501: Fix potential NULL pointer dereference )
Thanks,
Mukesh
>>> +
>>> lookup->dev_id = "i2c-gpio";
>>> if (iic->pin_sda < 32)
>>> lookup->table[0].chip_label = "SM501-LOW";
next prev parent reply other threads:[~2019-03-25 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 8:04 [PATCH] mfd: fix a potential NULL pointer dereference Kangjie Lu
2019-03-23 3:09 ` Kangjie Lu
2019-03-25 7:56 ` Lee Jones
2019-03-25 9:13 ` Mukesh Ojha [this message]
2019-04-02 7:08 ` 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=be967424-090f-d388-4530-47a9a817db1f@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=kjlu@umn.edu \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pakki001@umn.edu \
/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