From: Francesco Valla <francesco@valla.it>
To: Yuqiang Sun <izaiahsun@gmail.com>
Cc: andersson@kernel.org, mathieu.poirier@linaro.org,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] remoteproc: core: Do not put the device when device_add() fails
Date: Fri, 6 Nov 2026 12:32:39 +0100 [thread overview]
Message-ID: <au24I4glFZ0S30A5@bywater> (raw)
In-Reply-To: <20261106065100.44269-1-izaiahsun@gmail.com>
On Fri, Nov 06, 2026 at 02:51:00PM +0800, Yuqiang Sun wrote:
> In rproc_add(), put_device() is called when device_add() fails.
> But st_slim_rproc_alloc(), xlnx_r5_remoteproc and the other 23
> drivers (which use devm_rproc_alloc() and so devm_rproc_free()) then
> call rproc_free(), which puts the device again. The reference is
> dropped twice, and st_slim_rproc_alloc() uses the rproc after it is
> freed.
>
> Remove the put_device() in rproc_add() and add a comment saying why.
>
> Fixes: 7dbdb8bd7c02 ("remoteproc: core: Cleanup device in case of failure")
> Cc: stable@vger.kernel.org
> Signed-off-by: Yuqiang Sun <izaiahsun@gmail.com>
> ---
>
> Notes:
> Changes in v2:
> - Comment in the device_add() failure branch (Mathieu).
> - Shorter changelog.
> - Rebased on rproc-next.
>
> Bug was found by kbound, an internal static analysis prototype.
> The reproduction was assisted by Claude Opus 5.5.
>
> v1: https://lore.kernel.org/linux-remoteproc/20261029130037.5505-1-izaiahsun@gmail.com/
>
> drivers/remoteproc/remoteproc_core.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/remoteproc/remoteproc_core.c b/drivers/remoteproc/remoteproc_core.c
> index d5fa9d23bd5c..d0b1f6ee49d3 100644
> --- a/drivers/remoteproc/remoteproc_core.c
> +++ b/drivers/remoteproc/remoteproc_core.c
> @@ -2312,7 +2312,10 @@ int rproc_add(struct rproc *rproc)
>
> ret = device_add(dev);
> if (ret < 0) {
> - put_device(dev);
> + /*
> + * Do not put_device() here: the caller's rproc_free() does
> + * it, and the reference would be dropped twice.
> + */
> goto rproc_remove_cdev;
> }
>
>
> base-commit: b16b5a4fdf7d1f4ec15a53622d9b66081325fbf9
> --
> 2.53.0
>
>
Reviewed-by: Francesco Valla <francesco@valla.it>
Regards,
Francesco
prev parent reply other threads:[~2026-11-06 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 6:51 Yuqiang Sun
2026-11-06 11:32 ` Francesco Valla [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=au24I4glFZ0S30A5@bywater \
--to=francesco@valla.it \
--cc=andersson@kernel.org \
--cc=izaiahsun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=stable@vger.kernel.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 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®