From: Zhangfei Gao <zhangfei.gao@linaro.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Herbert Xu <herbert@gondor.apana.org.au>,
jean-philippe <jean-philippe@linaro.org>,
Wangzhou <wangzhou1@hisilicon.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: acc@openeuler.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, iommu@lists.linux.dev,
Zhangfei Gao <zhangfei.gao@linaro.org>,
Yang Shen <shenyang39@huawei.com>
Subject: [PATCH v2 1/2] uacce: Handle parent driver module removal
Date: Fri, 24 Jun 2022 22:21:21 +0800 [thread overview]
Message-ID: <20220624142122.30528-2-zhangfei.gao@linaro.org> (raw)
In-Reply-To: <20220624142122.30528-1-zhangfei.gao@linaro.org>
Change cdev owner to parent driver owner, which blocks rmmod parent
driver module once fd is opened.
Signed-off-by: Yang Shen <shenyang39@huawei.com>
Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
---
drivers/misc/uacce/uacce.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/uacce/uacce.c b/drivers/misc/uacce/uacce.c
index 281c54003edc..f82f2dd30e76 100644
--- a/drivers/misc/uacce/uacce.c
+++ b/drivers/misc/uacce/uacce.c
@@ -484,7 +484,7 @@ int uacce_register(struct uacce_device *uacce)
return -ENOMEM;
uacce->cdev->ops = &uacce_fops;
- uacce->cdev->owner = THIS_MODULE;
+ uacce->cdev->owner = uacce->parent->driver->owner;
return cdev_device_add(uacce->cdev, &uacce->dev);
}
--
2.36.1
next prev parent reply other threads:[~2022-06-24 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 14:21 [PATCH v2 0/2] fix uacce concurrency issue of uacce_remove Zhangfei Gao
2022-06-24 14:21 ` Zhangfei Gao [this message]
2022-06-27 13:21 ` [PATCH v2 1/2] uacce: Handle parent driver module removal Greg Kroah-Hartman
2022-06-27 14:14 ` Zhangfei Gao
2022-06-24 14:21 ` [PATCH v2 2/2] uacce: Handle parent device removal Zhangfei Gao
2022-06-24 14:37 ` [PATCH v2 0/2] fix uacce concurrency issue of uacce_remove Greg Kroah-Hartman
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=20220624142122.30528-2-zhangfei.gao@linaro.org \
--to=zhangfei.gao@linaro.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=acc@openeuler.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shenyang39@huawei.com \
--cc=wangzhou1@hisilicon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.