From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Dave Gerlach <d-gerlach@ti.com>
Cc: linux-kernel@vger.kernel.org, linux-remoteproc@vger.kernel.org,
Ohad Ben-Cohen <ohad@wizery.com>, Suman Anna <s-anna@ti.com>
Subject: Re: [PATCH] remoteproc: Fix potential race condition in rproc_add
Date: Tue, 14 Jun 2016 11:34:01 -0700 [thread overview]
Message-ID: <20160614183401.GT1256@tuxbot> (raw)
In-Reply-To: <9fb3ac21209aaa791882a5121f4c48153f0335b4.1464206136.git.d-gerlach@ti.com>
On Wed 25 May 13:41 PDT 2016, Dave Gerlach wrote:
> rproc_add adds the newly created remoteproc to a list for use by
> rproc_get_by_phandle and then does some additional processing to finish
> adding the remoteproc. This leaves a small window of time in which the
> rproc is available in the list but not yet fully initialized, so if
> another driver comes along and gets a handle to the rproc, it will be
> invalid. Rearrange the code in rproc_add to make sure the rproc is added
> to the list only after it has been successfuly initialized.
>
> Fixes: fec47d863587 ("remoteproc: introduce rproc_get_by_phandle API")
> Signed-off-by: Dave Gerlach <d-gerlach@ti.com>
Applied and added Cc: stable.
Regards,
Bjorn
> ---
> drivers/remoteproc/remoteproc_core.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
> index db3958b3f094..fe0539ed9cb5 100644
> --- a/drivers/remoteproc/remoteproc_core.c
> +++ b/drivers/remoteproc/remoteproc_core.c
> @@ -1264,11 +1264,6 @@ int rproc_add(struct rproc *rproc)
> if (ret < 0)
> return ret;
>
> - /* expose to rproc_get_by_phandle users */
> - mutex_lock(&rproc_list_mutex);
> - list_add(&rproc->node, &rproc_list);
> - mutex_unlock(&rproc_list_mutex);
> -
> dev_info(dev, "%s is available\n", rproc->name);
>
> dev_info(dev, "Note: remoteproc is still under development and considered experimental.\n");
> @@ -1276,8 +1271,16 @@ int rproc_add(struct rproc *rproc)
>
> /* create debugfs entries */
> rproc_create_debug_dir(rproc);
> + ret = rproc_add_virtio_devices(rproc);
> + if (ret < 0)
> + return ret;
>
> - return rproc_add_virtio_devices(rproc);
> + /* expose to rproc_get_by_phandle users */
> + mutex_lock(&rproc_list_mutex);
> + list_add(&rproc->node, &rproc_list);
> + mutex_unlock(&rproc_list_mutex);
> +
> + return 0;
> }
> EXPORT_SYMBOL(rproc_add);
>
prev parent reply other threads:[~2016-06-14 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 20:41 [PATCH] remoteproc: Fix potential race condition in rproc_add Dave Gerlach
2016-05-25 20:41 ` Dave Gerlach
2016-06-14 18:34 ` Bjorn Andersson [this message]
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=20160614183401.GT1256@tuxbot \
--to=bjorn.andersson@linaro.org \
--cc=d-gerlach@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=s-anna@ti.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.