From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Deepak Kumar Singh <quic_deesin@quicinc.com>
Cc: swboyd@chromium.org, quic_clew@quicinc.com,
mathieu.poirier@linaro.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
Ohad Ben-Cohen <ohad@wizery.com>
Subject: Re: [PATCH V1 3/3] rpmsg: glink: Add lock for ctrl device
Date: Fri, 11 Mar 2022 14:54:46 -0600 [thread overview]
Message-ID: <Yiu3Fl/Diw5iqh24@builder.lan> (raw)
In-Reply-To: <1643223886-28170-4-git-send-email-quic_deesin@quicinc.com>
On Wed 26 Jan 13:04 CST 2022, Deepak Kumar Singh wrote:
> Race between rpmsg_eptdev_create and rpmsg_chrdev_remove
> can sometime casue crash while accessing rpdev while new
> endpoint is being created. Using lock ensure no new eptdev
> is created after rpmsg_chrdev_remove has been completed.
This patch lacks a Signed-off-by.
Isn't this solving the same problem as the previous patch? Would be nice
with some more specifics on the race that you're seeing.
Thanks,
Bjorn
> ---
> drivers/rpmsg/rpmsg_char.c | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/rpmsg/rpmsg_char.c b/drivers/rpmsg/rpmsg_char.c
> index 2108ef8..3e5b85d 100644
> --- a/drivers/rpmsg/rpmsg_char.c
> +++ b/drivers/rpmsg/rpmsg_char.c
> @@ -27,6 +27,7 @@
>
> static dev_t rpmsg_major;
> static struct class *rpmsg_class;
> +struct mutex ctrl_lock;
>
> static DEFINE_IDA(rpmsg_ctrl_ida);
> static DEFINE_IDA(rpmsg_ept_ida);
> @@ -396,9 +397,12 @@ static int rpmsg_eptdev_create(struct rpmsg_ctrldev *ctrldev,
> struct device *dev;
> int ret;
>
> + mutex_lock(&ctrl_lock);
> eptdev = kzalloc(sizeof(*eptdev), GFP_KERNEL);
> - if (!eptdev)
> + if (!eptdev) {
> + mutex_unlock(&ctrl_lock);
> return -ENOMEM;
> + }
>
> dev = &eptdev->dev;
> eptdev->rpdev = rpdev;
> @@ -443,6 +447,7 @@ static int rpmsg_eptdev_create(struct rpmsg_ctrldev *ctrldev,
> put_device(dev);
> }
>
> + mutex_unlock(&ctrl_lock);
> return ret;
>
> free_ept_ida:
> @@ -453,6 +458,7 @@ static int rpmsg_eptdev_create(struct rpmsg_ctrldev *ctrldev,
> put_device(dev);
> kfree(eptdev);
>
> + mutex_unlock(&ctrl_lock);
> return ret;
> }
>
> @@ -525,6 +531,7 @@ static int rpmsg_chrdev_probe(struct rpmsg_device *rpdev)
> if (!ctrldev)
> return -ENOMEM;
>
> + mutex_init(&ctrl_lock);
> ctrldev->rpdev = rpdev;
>
> dev = &ctrldev->dev;
> @@ -581,12 +588,14 @@ static void rpmsg_chrdev_remove(struct rpmsg_device *rpdev)
> int ret;
>
> /* Destroy all endpoints */
> + mutex_lock(&ctrl_lock);
> ret = device_for_each_child(&ctrldev->dev, NULL, rpmsg_eptdev_destroy);
> if (ret)
> dev_warn(&rpdev->dev, "failed to nuke endpoints: %d\n", ret);
>
> device_del(&ctrldev->dev);
> put_device(&ctrldev->dev);
> + mutex_unlock(&ctrl_lock);
> }
>
> static struct rpmsg_driver rpmsg_chrdev_driver = {
> --
> 2.7.4
>
next prev parent reply other threads:[~2022-03-11 20:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 19:04 [PATCH V1 0/3] rpmsg char fixes for race conditions in device reboot Deepak Kumar Singh
2022-01-26 19:04 ` [PATCH V1 1/3] rpmsg: glink: Free device context only when cdev not in use Deepak Kumar Singh
2022-02-03 17:35 ` Mathieu Poirier
2022-02-14 15:02 ` Deepak Kumar Singh
2022-01-26 19:04 ` [PATCH V1 2/3] rpmsg: glink: Add lock to avoid race when rpmsg device is released Deepak Kumar Singh
2022-03-11 20:52 ` Bjorn Andersson
2022-04-07 16:58 ` Deepak Kumar Singh
2022-01-26 19:04 ` [PATCH V1 3/3] rpmsg: glink: Add lock for ctrl device Deepak Kumar Singh
2022-03-11 20:54 ` Bjorn Andersson [this message]
2022-04-06 11:38 ` Deepak Kumar Singh
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=Yiu3Fl/Diw5iqh24@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=ohad@wizery.com \
--cc=quic_clew@quicinc.com \
--cc=quic_deesin@quicinc.com \
--cc=swboyd@chromium.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 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.