public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Esben Haabendal <esben@geanix.com>
To: Zhang Changzhong <zhangchangzhong@huawei.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	Michal Simek <michal.simek@xilinx.com>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net] net: ll_temac: Fix potential NULL dereference in temac_probe()
Date: Tue, 08 Dec 2020 09:25:59 +0100	[thread overview]
Message-ID: <874kkw3drc.fsf@geanix.com> (raw)
In-Reply-To: <1607392422-20372-1-git-send-email-zhangchangzhong@huawei.com> (Zhang Changzhong's message of "Tue, 8 Dec 2020 09:53:42 +0800")

Zhang Changzhong <zhangchangzhong@huawei.com> writes:

> platform_get_resource() may fail and in this case a NULL dereference
> will occur.
>
> Fix it to use devm_platform_ioremap_resource() instead of calling
> platform_get_resource() and devm_ioremap().
>
> This is detected by Coccinelle semantic patch.
>
> @@
> expression pdev, res, n, t, e, e1, e2;
> @@
>
> res = \(platform_get_resource\|platform_get_resource_byname\)(pdev, t, n);
> + if (!res)
> +   return -EINVAL;
> ... when != res == NULL
> e = devm_ioremap(e1, res->start, e2);
>
> Fixes: 8425c41d1ef7 ("net: ll_temac: Extend support to non-device-tree platforms")
> Signed-off-by: Zhang Changzhong <zhangchangzhong@huawei.com>
> ---
>  drivers/net/ethernet/xilinx/ll_temac_main.c | 9 +++------
>  1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/ethernet/xilinx/ll_temac_main.c b/drivers/net/ethernet/xilinx/ll_temac_main.c
> index 60c199f..0301853 100644
> --- a/drivers/net/ethernet/xilinx/ll_temac_main.c
> +++ b/drivers/net/ethernet/xilinx/ll_temac_main.c
> @@ -1351,7 +1351,6 @@ static int temac_probe(struct platform_device *pdev)
>  	struct device_node *temac_np = dev_of_node(&pdev->dev), *dma_np;
>  	struct temac_local *lp;
>  	struct net_device *ndev;
> -	struct resource *res;
>  	const void *addr;
>  	__be32 *p;
>  	bool little_endian;
> @@ -1500,13 +1499,11 @@ static int temac_probe(struct platform_device *pdev)
>  		of_node_put(dma_np);
>  	} else if (pdata) {
>  		/* 2nd memory resource specifies DMA registers */
> -		res = platform_get_resource(pdev, IORESOURCE_MEM, 1);
> -		lp->sdma_regs = devm_ioremap(&pdev->dev, res->start,
> -						     resource_size(res));
> -		if (!lp->sdma_regs) {
> +		lp->sdma_regs = devm_platform_ioremap_resource(pdev, 1);
> +		if (IS_ERR(lp->sdma_regs)) {
>  			dev_err(&pdev->dev,
>  				"could not map DMA registers\n");
> -			return -ENOMEM;
> +			return PTR_ERR(lp->sdma_regs);
>  		}
>  		if (pdata->dma_little_endian) {
>  			lp->dma_in = temac_dma_in32_le;

Acked-by: Esben Haabendal <esben@geanix.com>

  reply	other threads:[~2020-12-08  8:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-08  1:53 [PATCH net] net: ll_temac: Fix potential NULL dereference in temac_probe() Zhang Changzhong
2020-12-08  8:25 ` Esben Haabendal [this message]
2020-12-09  0:16 ` David Miller

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=874kkw3drc.fsf@geanix.com \
    --to=esben@geanix.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@xilinx.com \
    --cc=netdev@vger.kernel.org \
    --cc=zhangchangzhong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox