From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Shengjiu Wang <shengjiu.wang@nxp.com>,
Fernando Guzman Lugo <fernando.lugo@ti.com>,
Ohad Ben-Cohen <ohad@wizery.com>
Cc: linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] remoteproc: Force shutdown during device removal
Date: Thu, 23 Jul 2026 12:54:58 +0200 [thread overview]
Message-ID: <413bcb02-4823-4c2f-8e0e-c9a40664caf9@oss.qualcomm.com> (raw)
In-Reply-To: <20260723-rproc-rmmod-not-crashing-v1-3-546dfd5de0e6@oss.qualcomm.com>
On 7/23/26 5:52 AM, Bjorn Andersson wrote:
> rproc_del() is subjected to the reference counted shutdown path, as such
> a remoteproc with more than one reference will be left running as its
> resources are released underneath it.
>
> Refactor the shutdown path such that the reference count value is
> ignored when called from rproc_del().
>
> Assisted-by: OpenCode:GPT-5.5
> Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
> ---
[...]
> +static int __rproc_shutdown(struct rproc *rproc, bool force)
> {
> struct device *dev = &rproc->dev;
> bool crashed;
> @@ -2029,9 +2008,10 @@ int rproc_shutdown(struct rproc *rproc)
> }
> crashed = rproc->state == RPROC_CRASHED;
>
> - /* if the remote proc is still needed, bail out */
> - if (!atomic_dec_and_test(&rproc->power))
> + if (!atomic_dec_and_test(&rproc->power) && !force) {
> + /* The remote processor is still needed by another user. */
> goto out;
> + }
GPT makes some unclear suggestions, effectively saying that rproc_shutdown(),
unlike other paths, seems not to first check whether the rproc is deleting
if the shutdown isn't forced. I think it's a valid concern.
Konrad
next prev parent reply other threads:[~2026-07-23 10:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 3:52 [PATCH 0/3] remoteproc: Improve removal of remoteproc drivers Bjorn Andersson
2026-07-23 3:52 ` [PATCH 1/3] remoteproc: Allow shutdown of crashed processors Bjorn Andersson
2026-07-23 9:34 ` Konrad Dybcio
2026-07-23 10:00 ` Mukesh Ojha
2026-07-23 3:52 ` [PATCH 2/3] remoteproc: Prevent crash handling to race with rproc_del() Bjorn Andersson
2026-07-23 10:09 ` Konrad Dybcio
2026-07-23 15:16 ` Mukesh Ojha
2026-07-23 22:29 ` Bjorn Andersson
2026-07-23 14:47 ` Mukesh Ojha
2026-07-23 15:19 ` Mukesh Ojha
2026-07-27 18:39 ` Pradnya Dahiwale
2026-07-28 1:18 ` Bjorn Andersson
2026-07-23 3:52 ` [PATCH 3/3] remoteproc: Force shutdown during device removal Bjorn Andersson
2026-07-23 9:59 ` Konrad Dybcio
2026-07-23 10:54 ` Konrad Dybcio [this message]
2026-07-23 16:12 ` Mukesh Ojha
2026-07-23 22:16 ` Bjorn Andersson
2026-07-27 18:47 ` Pradnya Dahiwale
2026-07-28 2:04 ` [PATCH 0/3] remoteproc: Improve removal of remoteproc drivers Bjorn Andersson
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=413bcb02-4823-4c2f-8e0e-c9a40664caf9@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=fernando.lugo@ti.com \
--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=shengjiu.wang@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®