From: Jia-Ju Bai <baijiaju1990@gmail.com>
To: vkoul@kernel.org, michal.simek@xilinx.com,
m.tretter@pengutronix.de, yukuai3@huawei.com, lars@metafoo.de,
libaokun1@huawei.com
Cc: dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Jia-Ju Bai <baijiaju1990@gmail.com>
Subject: [PATCH] dma: xilinx: check the return value of dma_set_mask() in zynqmp_dma_probe()
Date: Wed, 2 Mar 2022 18:43:34 -0800 [thread overview]
Message-ID: <20220303024334.813-1-baijiaju1990@gmail.com> (raw)
The function dma_set_mask() in zynqmp_dma_probe() can fail, so its
return value should be checked.
Fixes: b0cc417c1637 ("dmaengine: Add Xilinx zynqmp dma engine driver support")
Reported-by: TOTE Robot <oslab@tsinghua.edu.cn>
Signed-off-by: Jia-Ju Bai <baijiaju1990@gmail.com>
---
drivers/dma/xilinx/zynqmp_dma.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/dma/xilinx/zynqmp_dma.c b/drivers/dma/xilinx/zynqmp_dma.c
index 7aa63b652027..963fb1de93af 100644
--- a/drivers/dma/xilinx/zynqmp_dma.c
+++ b/drivers/dma/xilinx/zynqmp_dma.c
@@ -1050,7 +1050,8 @@ static int zynqmp_dma_probe(struct platform_device *pdev)
zdev->dev = &pdev->dev;
INIT_LIST_HEAD(&zdev->common.channels);
- dma_set_mask(&pdev->dev, DMA_BIT_MASK(44));
+ if (dma_set_mask(&pdev->dev, DMA_BIT_MASK(44)))
+ return -EIO;
dma_cap_set(DMA_MEMCPY, zdev->common.cap_mask);
p = &zdev->common;
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-03-03 2:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 2:43 Jia-Ju Bai [this message]
2022-03-04 8:20 ` [PATCH] dma: xilinx: check the return value of dma_set_mask() in zynqmp_dma_probe() Michael Tretter
2022-03-05 8:38 ` Jia-Ju Bai
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=20220303024334.813-1-baijiaju1990@gmail.com \
--to=baijiaju1990@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=libaokun1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
--cc=michal.simek@xilinx.com \
--cc=vkoul@kernel.org \
--cc=yukuai3@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;
as well as URLs for NNTP newsgroup(s).