From: Ray Jui <ray.jui@broadcom.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH -next] pinctrl: nsp: fix potential NULL dereference in nsp_pinmux_probe()
Date: Fri, 13 Jul 2018 16:53:29 +0000 [thread overview]
Message-ID: <14329d52-72bb-3594-dec3-00ab0f7ccd40@broadcom.com> (raw)
In-Reply-To: <CACRpkdbwAJOaFay3x45gyf7rBpkPOAMbxW6FLQUvCekUKatLYA@mail.gmail.com>
Hi Linus,
On 7/13/2018 12:46 AM, Linus Walleij wrote:
> On Wed, Jul 11, 2018 at 2:25 PM Wei Yongjun <weiyongjun1@huawei.com> wrote:
>
>> platform_get_resource() may fail and return NULL, so we should
>> better check it's return value to avoid a NULL pointer dereference
>> a bit later in the code.
>>
>> This is detected by Coccinelle semantic patch.
>>
>> @@
>> expression pdev, res, n, t, e, e1, e2;
>> @@
>>
>> res = platform_get_resource(pdev, t, n);
>> + if (!res)
>> + return -EINVAL;
>> ... when != res = NULL
>> e = devm_ioremap_nocache(e1, res->start, e2);
>>
>> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
>
> Patch applied with Ray's ACK.
Would be nice to add the following Fixes tag:
Fixes: cc4fa83f66e9 ("pinctrl: nsp: add pinmux driver support for
Broadcom NSP SoC")
Thanks,
Ray
>
> Yours,
> Linus Walleij
>
next prev parent reply other threads:[~2018-07-13 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 12:34 [PATCH -next] pinctrl: nsp: fix potential NULL dereference in nsp_pinmux_probe() Wei Yongjun
2018-07-11 16:48 ` Ray Jui
2018-07-11 16:56 ` Ray Jui
2018-07-11 17:01 ` Sudeep Holla
2018-07-11 17:11 ` Ray Jui
2018-07-11 17:14 ` Sudeep Holla
2018-07-11 17:18 ` Ray Jui
2018-07-13 7:46 ` Linus Walleij
2018-07-13 16:53 ` Ray Jui [this message]
2018-07-14 10:49 ` Linus Walleij
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=14329d52-72bb-3594-dec3-00ab0f7ccd40@broadcom.com \
--to=ray.jui@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.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