From: Alban <albeu@free.fr>
To: Wei Yongjun <weiyongjun1@huawei.com>
Cc: Aban Bedel <albeu@free.fr>,
Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH -next] gpio: ath79: Fix potential NULL dereference in ath79_gpio_probe()
Date: Fri, 5 Jan 2018 15:06:38 +0100 [thread overview]
Message-ID: <20180105150638.2e483d0d@tock> (raw)
In-Reply-To: <1515047483-168600-1-git-send-email-weiyongjun1@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]
On Thu, 4 Jan 2018 06:31:23 +0000
Wei Yongjun <weiyongjun1@huawei.com> wrote:
> platform_get_resource() may return NULL, add proper
> check to avoid potential NULL dereferencing.
>
> 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(e1, res->start, e2);
>
> Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
> ---
> drivers/gpio/gpio-ath79.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpio/gpio-ath79.c b/drivers/gpio/gpio-ath79.c
> index a757171..0bebcba 100644
> --- a/drivers/gpio/gpio-ath79.c
> +++ b/drivers/gpio/gpio-ath79.c
> @@ -258,6 +258,8 @@ static int ath79_gpio_probe(struct platform_device *pdev)
> }
>
> res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> + if (!res)
> + return -EINVAL;
> ctrl->base = devm_ioremap(&pdev->dev, res->start, resource_size(res));
> if (!ctrl->base)
> return -ENOMEM;
This fix is needed, however this patch is not against the current
version. The current version use res in a call to devm_ioremap_nocache()
and not devm_ioremap().
Alban
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2018-01-05 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 6:31 [PATCH -next] gpio: ath79: Fix potential NULL dereference in ath79_gpio_probe() Wei Yongjun
2018-01-05 14:06 ` Alban [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=20180105150638.2e483d0d@tock \
--to=albeu@free.fr \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=weiyongjun1@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.