From: Chenghai Huang <huangchenghai2@huawei.com>
To: <gregkh@linuxfoundation.org>, <zhangfei.gao@linaro.org>,
<wangzhou1@hisilicon.com>
Cc: <linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>,
<linux-crypto@vger.kernel.org>, <fanghao11@huawei.com>,
<shenyang39@huawei.com>, <qianweili@huawei.com>,
<linwenkai6@hisilicon.com>, <liulongfang@huawei.com>
Subject: [PATCH 1/4] uacce: fix for cdev memory leak
Date: Fri, 22 Aug 2025 18:39:01 +0800 [thread overview]
Message-ID: <20250822103904.3776304-2-huangchenghai2@huawei.com> (raw)
In-Reply-To: <20250822103904.3776304-1-huangchenghai2@huawei.com>
From: Wenkai Lin <linwenkai6@hisilicon.com>
If adding uacce cdev to the system fails, it could be due to two
reasons: either the device's devt exists when the failure occurs,
or the device_add operation fails. In the latter case, cdev_del
will be executed, but in the former case, it will not, leading to a
resource leak. Therefore, it is necessary to perform the cdev_del
action during abnormal exit.
Fixes: 015d239ac014 ("uacce: add uacce driver")
Signed-off-by: Wenkai Lin <linwenkai6@hisilicon.com>
Signed-off-by: Chenghai Huang <huangchenghai2@huawei.com>
---
drivers/misc/uacce/uacce.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/misc/uacce/uacce.c b/drivers/misc/uacce/uacce.c
index 42e7d2a2a90c..3604f722ed60 100644
--- a/drivers/misc/uacce/uacce.c
+++ b/drivers/misc/uacce/uacce.c
@@ -519,6 +519,8 @@ EXPORT_SYMBOL_GPL(uacce_alloc);
*/
int uacce_register(struct uacce_device *uacce)
{
+ int ret;
+
if (!uacce)
return -ENODEV;
@@ -529,7 +531,14 @@ int uacce_register(struct uacce_device *uacce)
uacce->cdev->ops = &uacce_fops;
uacce->cdev->owner = THIS_MODULE;
- return cdev_device_add(uacce->cdev, &uacce->dev);
+ ret = cdev_device_add(uacce->cdev, &uacce->dev);
+ if (ret) {
+ cdev_del(uacce->cdev);
+ uacce->cdev = NULL;
+ return ret;
+ }
+
+ return 0;
}
EXPORT_SYMBOL_GPL(uacce_register);
--
2.33.0
next prev parent reply other threads:[~2025-08-22 10:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 10:39 [PATCH 0/4] uacce: driver fixes for memory leaks and state management Chenghai Huang
2025-08-22 10:39 ` Chenghai Huang [this message]
2025-08-22 11:27 ` [PATCH 1/4] uacce: fix for cdev memory leak Greg KH
2025-09-13 10:43 ` huangchenghai
2025-08-25 8:20 ` Zhangfei Gao
2025-08-28 12:59 ` linwenkai (C)
2025-08-22 10:39 ` [PATCH 2/4] uacce: fix isolate sysfs check condition Chenghai Huang
2025-08-22 10:39 ` [PATCH 3/4] uacce: implement mremap in uacce_vm_ops to return -EPERM Chenghai Huang
2025-08-22 11:46 ` Greg KH
2025-08-28 5:59 ` Zhangfei Gao
2025-09-06 12:03 ` Greg KH
2025-09-08 6:33 ` Zhangfei Gao
2025-09-13 10:40 ` huangchenghai
2025-09-13 11:06 ` Greg KH
2025-09-15 1:48 ` huangchenghai
2025-08-22 10:39 ` [PATCH 4/4] uacce: ensure safe queue release with state management Chenghai Huang
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=20250822103904.3776304-2-huangchenghai2@huawei.com \
--to=huangchenghai2@huawei.com \
--cc=fanghao11@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=linwenkai6@hisilicon.com \
--cc=liulongfang@huawei.com \
--cc=qianweili@huawei.com \
--cc=shenyang39@huawei.com \
--cc=wangzhou1@hisilicon.com \
--cc=zhangfei.gao@linaro.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®