From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Dongliang Mu <mudongliangabcd@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memory: fsl_ifc: fix leak of irq and nand_irq in fsl_ifc_ctrl_probe
Date: Tue, 3 Aug 2021 09:57:41 +0200 [thread overview]
Message-ID: <81ccbbb5-5499-7a75-88ba-bae5328ffbf9@canonical.com> (raw)
In-Reply-To: <20210803075159.2823913-1-mudongliangabcd@gmail.com>
On 03/08/2021 09:51, Dongliang Mu wrote:
> In fsl_ifc_ctrl_probe, if fsl_ifc_ctrl_init fails, we should free the
> resources allocated by irq_of_parse_and_map.
Your code is doing much more. You also touch nand_irq, not only
fsl_ifc_ctrl_init(). This looks incorrect as IRQ is optional, isn't it?
The problem is entirely different than you described here - the error
paths of fsl_ifc_ctrl_init() and request_irq() are wrong. They do not
release resources in proper paths.
Best regards,
Krzysztof
>
> Fix this by adjusting the error handling code.
>
> Signed-off-by: Dongliang Mu <mudongliangabcd@gmail.com>
> ---
> drivers/memory/fsl_ifc.c | 19 ++++++++++++-------
> 1 file changed, 12 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/memory/fsl_ifc.c b/drivers/memory/fsl_ifc.c
> index d062c2f8250f..391390dd3dcb 100644
> --- a/drivers/memory/fsl_ifc.c
> +++ b/drivers/memory/fsl_ifc.c
> @@ -258,12 +258,17 @@ static int fsl_ifc_ctrl_probe(struct platform_device *dev)
> /* get the nand machine irq */
> fsl_ifc_ctrl_dev->nand_irq =
> irq_of_parse_and_map(dev->dev.of_node, 1);
> + if (fsl_ifc_ctrl_dev->nand_irq == 0) {
> + dev_err(&dev->dev, "failed to get nand_irq resource for IFC\n");
> + ret = -ENODEV;
> + goto err_unmap_irq;
> + }
>
> fsl_ifc_ctrl_dev->dev = &dev->dev;
>
> ret = fsl_ifc_ctrl_init(fsl_ifc_ctrl_dev);
> if (ret < 0)
> - goto err;
> + goto err_unmap_nandirq;
>
> init_waitqueue_head(&fsl_ifc_ctrl_dev->nand_wait);
>
> @@ -272,7 +277,7 @@ static int fsl_ifc_ctrl_probe(struct platform_device *dev)
> if (ret != 0) {
> dev_err(&dev->dev, "failed to install irq (%d)\n",
> fsl_ifc_ctrl_dev->irq);
> - goto err_irq;
> + goto err_unmap_nandirq;
> }
>
> if (fsl_ifc_ctrl_dev->nand_irq) {
> @@ -281,17 +286,17 @@ static int fsl_ifc_ctrl_probe(struct platform_device *dev)
> if (ret != 0) {
> dev_err(&dev->dev, "failed to install irq (%d)\n",
> fsl_ifc_ctrl_dev->nand_irq);
> - goto err_nandirq;
> + goto err_free_irq;
> }
> }
>
> return 0;
>
> -err_nandirq:
> - free_irq(fsl_ifc_ctrl_dev->nand_irq, fsl_ifc_ctrl_dev);
> - irq_dispose_mapping(fsl_ifc_ctrl_dev->nand_irq);
> -err_irq:
> +err_free_irq:
> free_irq(fsl_ifc_ctrl_dev->irq, fsl_ifc_ctrl_dev);
> +err_unmap_nandirq:
> + irq_dispose_mapping(fsl_ifc_ctrl_dev->nand_irq);
> +err_unmap_irq:
> irq_dispose_mapping(fsl_ifc_ctrl_dev->irq);
> err:
> iounmap(fsl_ifc_ctrl_dev->gregs);
>
next prev parent reply other threads:[~2021-08-03 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 7:51 Dongliang Mu
2021-08-03 7:57 ` Krzysztof Kozlowski [this message]
2021-08-03 9:28 ` Dongliang Mu
2021-08-03 9:51 ` Krzysztof Kozlowski
2021-08-03 10:55 ` Dongliang Mu
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=81ccbbb5-5499-7a75-88ba-bae5328ffbf9@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mudongliangabcd@gmail.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 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®