From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Zheng Yongjun <zhengyongjun3@huawei.com>
Cc: mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
linux-input@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: fix reference leak in stmfts_input_open
Date: Sun, 20 Mar 2022 21:57:34 -0700 [thread overview]
Message-ID: <YjgFvv5uVC42J1aY@google.com> (raw)
In-Reply-To: <20220317131604.53538-1-zhengyongjun3@huawei.com>
On Thu, Mar 17, 2022 at 01:16:04PM +0000, Zheng Yongjun wrote:
> pm_runtime_get_sync() will increment pm usage counter even it
> failed. Forgetting to call pm_runtime_put_noidle will result
> in reference leak in stmfts_input_open, so we should fix it.
>
> Signed-off-by: Zheng Yongjun <zhengyongjun3@huawei.com>
Applied, thank you.
--
Dmitry
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Zheng Yongjun <zhengyongjun3@huawei.com>
Cc: mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
linux-input@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: fix reference leak in stmfts_input_open
Date: Sun, 20 Mar 2022 21:57:34 -0700 [thread overview]
Message-ID: <YjgFvv5uVC42J1aY@google.com> (raw)
In-Reply-To: <20220317131604.53538-1-zhengyongjun3@huawei.com>
On Thu, Mar 17, 2022 at 01:16:04PM +0000, Zheng Yongjun wrote:
> pm_runtime_get_sync() will increment pm usage counter even it
> failed. Forgetting to call pm_runtime_put_noidle will result
> in reference leak in stmfts_input_open, so we should fix it.
>
> Signed-off-by: Zheng Yongjun <zhengyongjun3@huawei.com>
Applied, thank you.
--
Dmitry
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-21 4:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 13:16 [PATCH] Input: fix reference leak in stmfts_input_open Zheng Yongjun
2022-03-17 13:16 ` Zheng Yongjun
2022-03-21 4:57 ` Dmitry Torokhov [this message]
2022-03-21 4:57 ` Dmitry Torokhov
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=YjgFvv5uVC42J1aY@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=zhengyongjun3@huawei.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.