From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Matthias Kaehlcke <mka@chromium.org>,
Andy Gross <agross@kernel.org>, Ohad Ben-Cohen <ohad@wizery.com>
Cc: Sujit Kautkar <sujitka@chromium.org>,
linux-kernel@vger.kernel.org, Stephen Boyd <swboyd@chromium.org>,
linux-remoteproc@vger.kernel.org,
Sibi Sankar <sibis@codeaurora.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>
Subject: Re: [PATCH v6 1/2] rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev
Date: Mon, 17 Jan 2022 16:46:59 -0600 [thread overview]
Message-ID: <164245960510.1698571.4998090450663669237.b4-ty@linaro.org> (raw)
In-Reply-To: <20220110104706.v6.1.Iaac908f3e3149a89190ce006ba166e2d3fd247a3@changeid>
On Mon, 10 Jan 2022 10:47:36 -0800, Matthias Kaehlcke wrote:
> From: Sujit Kautkar <sujitka@chromium.org>
>
> struct rpmsg_ctrldev contains a struct cdev. The current code frees
> the rpmsg_ctrldev struct in rpmsg_ctrldev_release_device(), but the
> cdev is a managed object, therefore its release is not predictable
> and the rpmsg_ctrldev could be freed before the cdev is entirely
> released, as in the backtrace below.
>
> [...]
Applied, thanks!
[1/2] rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev
commit: b7fb2dad571d1e21173c06cef0bced77b323990a
[2/2] rpmsg: char: Fix race between the release of rpmsg_eptdev and cdev
commit: 7a534ae89e34e9b51acb5a63dd0f88308178b46a
Best regards,
--
Bjorn Andersson <bjorn.andersson@linaro.org>
prev parent reply other threads:[~2022-01-17 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 18:47 [PATCH v6 1/2] rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev Matthias Kaehlcke
2022-01-10 18:47 ` [PATCH v6 2/2] rpmsg: char: Fix race between the release of rpmsg_eptdev " Matthias Kaehlcke
2022-01-10 18:56 ` Bjorn Andersson
2022-01-10 21:09 ` Stephen Boyd
2022-01-10 21:09 ` [PATCH v6 1/2] rpmsg: char: Fix race between the release of rpmsg_ctrldev " Stephen Boyd
2022-01-17 22:46 ` 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=164245960510.1698571.4998090450663669237.b4-ty@linaro.org \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mka@chromium.org \
--cc=ohad@wizery.com \
--cc=sibis@codeaurora.org \
--cc=sujitka@chromium.org \
--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.