From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Miaoqian Lin <linmq006@gmail.com>,
Sergey Shtylyov <s.shtylyov@omp.ru>,
Jeff Garzik <jgarzik@redhat.com>,
David Daney <david.daney@cavium.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ata: pata_octeon_cf: Fix refcount leak in octeon_cf_probe
Date: Thu, 2 Jun 2022 15:32:24 +0900 [thread overview]
Message-ID: <87953d70-198d-e146-b67d-b320603d52d3@opensource.wdc.com> (raw)
In-Reply-To: <20220601085926.45183-1-linmq006@gmail.com>
On 2022/06/01 17:59, Miaoqian Lin wrote:
> of_find_device_by_node() takes reference, we should use put_device()
> to release it when not need anymore.
> Add missing put_device() to avoid refcount leak.
>
> Fixes: 43f01da0f279 ("MIPS/OCTEON/ata: Convert pata_octeon_cf.c to use device tree.")
> Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
> ---
> changes in v2:
> - Add put_device() at the end of if (dma_dev).
> we need the null check and do handling only if dma_dev!=NULL.
> - call put_device before of_node_put() in error path. keep the
> reverse order of resource allocation.
>
> v1 link:
> https://lore.kernel.org/all/20220511062723.56652-1-linmq006@gmail.com/
> ---
> drivers/ata/pata_octeon_cf.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/ata/pata_octeon_cf.c b/drivers/ata/pata_octeon_cf.c
> index 6b5ed3046b44..35608a0cf552 100644
> --- a/drivers/ata/pata_octeon_cf.c
> +++ b/drivers/ata/pata_octeon_cf.c
> @@ -856,12 +856,14 @@ static int octeon_cf_probe(struct platform_device *pdev)
> int i;
> res_dma = platform_get_resource(dma_dev, IORESOURCE_MEM, 0);
> if (!res_dma) {
> + put_device(&dma_dev->dev);
> of_node_put(dma_node);
> return -EINVAL;
> }
> cf_port->dma_base = (u64)devm_ioremap(&pdev->dev, res_dma->start,
> resource_size(res_dma));
> if (!cf_port->dma_base) {
> + put_device(&dma_dev->dev);
> of_node_put(dma_node);
> return -EINVAL;
> }
> @@ -871,6 +873,7 @@ static int octeon_cf_probe(struct platform_device *pdev)
> irq = i;
> irq_handler = octeon_cf_interrupt;
> }
> + put_device(&dma_dev->dev);
> }
> of_node_put(dma_node);
> }
Applied to for-5.19-fixes. Thanks !
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2022-06-02 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 8:59 Miaoqian Lin
2022-06-01 19:01 ` Sergey Shtylyov
2022-06-02 6:32 ` Damien Le Moal [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=87953d70-198d-e146-b67d-b320603d52d3@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=david.daney@cavium.com \
--cc=jgarzik@redhat.com \
--cc=linmq006@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
/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®