From: Eugen Hristev <eugen.hristev@linaro.org>
To: Charles Han <hanchunchao@inspur.com>,
vkoul@kernel.org, vz@mleia.com, manabian@gmail.com
Cc: dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: Add NULL check in lpc18xx_dmamux_reserve()
Date: Mon, 16 Jun 2025 09:57:34 +0300 [thread overview]
Message-ID: <dd2bf2eb-d0a0-4bc4-b4be-a60a671222f9@linaro.org> (raw)
In-Reply-To: <20250616060212.1560-1-hanchunchao@inspur.com>
On 6/16/25 09:02, Charles Han wrote:
> The function of_find_device_by_node() may return NULL if the device
> node is not found or CONFIG_OF not defined.
> Add check whether the return value is NULL and set the error code
> to be returned as -ENODEV.
>
> Fixes: e5f4ae84be74 ("dmaengine: add driver for lpc18xx dmamux")
> Signed-off-by: Charles Han <hanchunchao@inspur.com>
> ---
> drivers/dma/lpc18xx-dmamux.c | 9 +++++++--
> 1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/dma/lpc18xx-dmamux.c b/drivers/dma/lpc18xx-dmamux.c
> index 2b6436f4b193..ef9aed4ba173 100644
> --- a/drivers/dma/lpc18xx-dmamux.c
> +++ b/drivers/dma/lpc18xx-dmamux.c
> @@ -53,11 +53,16 @@ static void lpc18xx_dmamux_free(struct device *dev, void *route_data)
> static void *lpc18xx_dmamux_reserve(struct of_phandle_args *dma_spec,
> struct of_dma *ofdma)
> {
> - struct platform_device *pdev = of_find_device_by_node(ofdma->of_node);
> - struct lpc18xx_dmamux_data *dmamux = platform_get_drvdata(pdev);
> unsigned long flags;
> unsigned mux;
>
> + struct platform_device *pdev = of_find_device_by_node(ofdma->of_node);
> +
> + if (!pdev)
> + return ERR_PTR(-ENODEV);
> +
> + struct lpc18xx_dmamux_data *dmamux = platform_get_drvdata(pdev);
I believe you should still declare all the variables at the beginning of
the function, even if you initialize them later.
> +
> if (dma_spec->args_count != 3) {
> dev_err(&pdev->dev, "invalid number of dma mux args\n");
> return ERR_PTR(-EINVAL);
prev parent reply other threads:[~2025-06-16 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 6:02 Charles Han
2025-06-16 6:57 ` Eugen Hristev [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=dd2bf2eb-d0a0-4bc4-b4be-a60a671222f9@linaro.org \
--to=eugen.hristev@linaro.org \
--cc=dmaengine@vger.kernel.org \
--cc=hanchunchao@inspur.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manabian@gmail.com \
--cc=vkoul@kernel.org \
--cc=vz@mleia.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
all inboxes | Powered by JetHome®