linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qinglang Miao <miaoqinglang@huawei.com>
To: Vinod Koul <vkoul@kernel.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Alexandre Torgue <alexandre.torgue@st.com>
Cc: <dmaengine@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	Qinglang Miao <miaoqinglang@huawei.com>
Subject: [PATCH 0/3] dmaengine: stm32: fix reference leak
Date: Fri, 27 Nov 2020 17:45:22 +0800	[thread overview]
Message-ID: <20201127094525.121388-1-miaoqinglang@huawei.com> (raw)

pm_runtime_get_sync will increment pm usage counter even it
failed. Forgetting to putting operation will result in a
reference leak here. 

Use pm_runtime_resume_and_get to fix it.

Qinglang Miao (3):
  dmaengine: stm32-dma: fix reference leak in stm32_dma
  dmaengine: stm32-dmamux: fix reference leak in stm32_dmamux
  dmaengine: stm32-mdma: fix reference leak in stm32-mdma

 drivers/dma/stm32-dma.c    | 4 ++--
 drivers/dma/stm32-dmamux.c | 6 +++---
 drivers/dma/stm32-mdma.c   | 4 ++--
 3 files changed, 7 insertions(+), 7 deletions(-)

-- 
2.23.0


             reply	other threads:[~2020-11-27  9:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27  9:45 Qinglang Miao [this message]
2020-11-27  9:45 ` [PATCH 1/3] dmaengine: stm32-dma: fix reference leak in stm32_dma Qinglang Miao
2020-11-27  9:45 ` [PATCH 2/3] dmaengine: stm32-dmamux: fix reference leak in stm32_dmamux Qinglang Miao
2020-11-27  9:45 ` [PATCH 3/3] dmaengine: stm32-mdma: fix reference leak in stm32-mdma Qinglang Miao

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=20201127094525.121388-1-miaoqinglang@huawei.com \
    --to=miaoqinglang@huawei.com \
    --cc=alexandre.torgue@st.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=vkoul@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;
as well as URLs for NNTP newsgroup(s).