aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Lew <[email protected]>2020-07-30 10:48:15 +0530
committerBjorn Andersson <[email protected]>2021-10-15 11:01:14 -0500
commit343ba27b6f9d473ec3e602cc648300eb03a7fa05 (patch)
tree778644f3ad902ade013279211e42788b92c55efc
parentc7c182d4447e172f87e37d6c04879b94b8635b37 (diff)
rpmsg: glink: Remove channel decouple from rpdev release
If a channel is being rapidly restarting and the kobj release worker is busy, there is a chance the rpdev_release function will run after the channel struct itself has been released. There should not be a need to decouple the channel from rpdev in the rpdev release since that should only happen from the close commands. Signed-off-by: Chris Lew <[email protected]> Signed-off-by: Deepak Kumar Singh <[email protected]> Signed-off-by: Bjorn Andersson <[email protected]> Link: https://lore.kernel.org/r/[email protected]
-rw-r--r--drivers/rpmsg/qcom_glink_native.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/drivers/rpmsg/qcom_glink_native.c b/drivers/rpmsg/qcom_glink_native.c
index ac710dc03710..c1207aa88bdf 100644
--- a/drivers/rpmsg/qcom_glink_native.c
+++ b/drivers/rpmsg/qcom_glink_native.c
@@ -1417,9 +1417,7 @@ static const struct rpmsg_endpoint_ops glink_endpoint_ops = {
static void qcom_glink_rpdev_release(struct device *dev)
{
struct rpmsg_device *rpdev = to_rpmsg_device(dev);
- struct glink_channel *channel = to_glink_channel(rpdev->ept);
- channel->rpdev = NULL;
kfree(rpdev);
}