From: Mikhail Arkhipov <m.arhipov@rosa.ru>
To: Peter Ujfalusi <peter.ujfalusi@gmail.com>
Cc: Mikhail Arkhipov <m.arhipov@rosa.ru>,
Vinod Koul <vkoul@kernel.org>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: [PATCH] dmaengine: ti: edma: Check return value of of_dma_controller_register
Date: Mon, 23 Sep 2024 22:37:03 +0300 [thread overview]
Message-ID: <20240923193703.36645-1-m.arhipov@rosa.ru> (raw)
If of_dma_controller_register() fails within the edma_probe() function,
the driver does not check the return value or log the failure. This
oversight can cause other drivers that rely on this DMA controller to fail
during their probe phase. Specifically, when other drivers call
of_dma_request_slave_channel(), they may receive an error code
-EPROBE_DEFER, causing their initialization to be delayed or fail without
clear logging of the root cause.
Add a check for the return value of of_dma_controller_register() in the
edma_probe() function. If the function returns an error, log an appropriate
error message and handle the failure by cleaning up resources and returning
the error code. This ensures that the failure is properly reported, which
aids in debugging and maintains system stability.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Fixes: dc9b60552f6a ("ARM/dmaengine: edma: Move of_dma_controller_register to the dmaengine driver")
Signed-off-by: Mikhail Arkhipov <m.arhipov@rosa.ru>
---
drivers/dma/ti/edma.c | 17 +++++++++++++----
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/drivers/dma/ti/edma.c b/drivers/dma/ti/edma.c
index 5f8d2e93ff3f..9fcbd97d346f 100644
--- a/drivers/dma/ti/edma.c
+++ b/drivers/dma/ti/edma.c
@@ -2529,18 +2529,27 @@ static int edma_probe(struct platform_device *pdev)
if (ret) {
dev_err(dev, "memcpy ddev registration failed (%d)\n",
ret);
- dma_async_device_unregister(&ecc->dma_slave);
- goto err_reg1;
+ goto err_unregister_dma_slave;
}
}
- if (node)
- of_dma_controller_register(node, of_edma_xlate, ecc);
+ if (node) {
+ ret = of_dma_controller_register(node, of_edma_xlate, ecc);
+ if (ret) {
+ dev_err(dev, "Failed to register DMA controller (%d)\n", ret);
+ goto err_unregister_dma_memcpy;
+ }
+ }
dev_info(dev, "TI EDMA DMA engine driver\n");
return 0;
+err_unregister_dma_memcpy:
+ if (ecc->dma_memcpy)
+ dma_async_device_unregister(ecc->dma_memcpy);
+err_unregister_dma_slave:
+ dma_async_device_unregister(&ecc->dma_slave);
err_reg1:
edma_free_slot(ecc, ecc->dummy_slot);
err_disable_pm:
--
2.39.3 (Apple Git-146)
next reply other threads:[~2024-09-23 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 19:37 Mikhail Arkhipov [this message]
2024-09-25 16:14 ` Péter Ujfalusi
2024-10-22 5:32 ` Vinod Koul
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=20240923193703.36645-1-m.arhipov@rosa.ru \
--to=m.arhipov@rosa.ru \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=peter.ujfalusi@gmail.com \
--cc=vkoul@kernel.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
all inboxes | Powered by JetHome®