From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Hangyu Hua <hbh25y@gmail.com>
Cc: bjorn.andersson@linaro.org, gregkh@linuxfoundation.org,
krzysztof.kozlowski@linaro.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] rpmsg: fix possible refcount leak in rpmsg_register_device_override()
Date: Fri, 24 Jun 2022 11:36:21 -0600 [thread overview]
Message-ID: <20220624173621.GC1736477@p14s> (raw)
In-Reply-To: <20220624024120.11576-1-hbh25y@gmail.com>
On Fri, Jun 24, 2022 at 10:41:20AM +0800, Hangyu Hua wrote:
> rpmsg_register_device_override need to call put_device to free vch when
> driver_set_override fails.
>
> Fix this by adding a put_device() to the error path.
>
> Fixes: bb17d110cbf2 ("rpmsg: Fix calling device_lock() on non-initialized device")
This is funny... Neither Bjorn nor I have reviewed this patch...
> Signed-off-by: Hangyu Hua <hbh25y@gmail.com>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
>
> v2: change the commit log.
>
> drivers/rpmsg/rpmsg_core.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/rpmsg/rpmsg_core.c b/drivers/rpmsg/rpmsg_core.c
> index 290c1f02da10..5a47cad89fdc 100644
> --- a/drivers/rpmsg/rpmsg_core.c
> +++ b/drivers/rpmsg/rpmsg_core.c
> @@ -618,6 +618,7 @@ int rpmsg_register_device_override(struct rpmsg_device *rpdev,
> strlen(driver_override));
> if (ret) {
> dev_err(dev, "device_set_override failed: %d\n", ret);
> + put_device(dev);
Applied.
Thanks,
Mathieu
> return ret;
> }
> }
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-06-24 17:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 2:41 [PATCH v2] rpmsg: fix possible refcount leak in rpmsg_register_device_override() Hangyu Hua
2022-06-24 17:36 ` Mathieu Poirier [this message]
2022-06-24 17:45 ` Krzysztof Kozlowski
2022-06-24 18:43 ` Mathieu Poirier
2022-06-25 19:40 ` Krzysztof Kozlowski
2022-06-25 19:49 ` Krzysztof Kozlowski
2022-06-28 16:31 ` Mathieu Poirier
2022-06-29 8:01 ` Krzysztof Kozlowski
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=20220624173621.GC1736477@p14s \
--to=mathieu.poirier@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=hbh25y@gmail.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@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 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.