From: Andreas Platschek <andreas.platschek@opentech.at>
To: vinod.koul@intel.com
Cc: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
dan.j.williams@intel.com
Subject: Re: [PATCH] dmaengine: fsl-edma: disable clks on all error paths
Date: Wed, 6 Dec 2017 14:20:45 +0100 [thread overview]
Message-ID: <20171206132045.GA5040@opentech.at> (raw)
In-Reply-To: <1512558813-25279-1-git-send-email-andreas.platschek@opentech.at>
Hi,
On Wed, 06 Dec 2017, Andreas Platschek wrote:
> Previously enabled clks are only disabled if clk_prepare_enable() fails.
> However, there are other error paths were the previously enabled
> clocks are not disabled.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Andreas Platschek <andreas.platschek@opentech.at>
> ---
> drivers/dma/fsl-edma.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/dma/fsl-edma.c b/drivers/dma/fsl-edma.c
> index 6775f2c74e25..ccb447253cd2 100644
> --- a/drivers/dma/fsl-edma.c
> +++ b/drivers/dma/fsl-edma.c
> @@ -904,12 +904,23 @@ static int fsl_edma_probe(struct platform_device *pdev)
>
> res = platform_get_resource(pdev, IORESOURCE_MEM, 1 + i);
> fsl_edma->muxbase[i] = devm_ioremap_resource(&pdev->dev, res);
> - if (IS_ERR(fsl_edma->muxbase[i]))
> + if (IS_ERR(fsl_edma->muxbase[i])) {
> + /* disable only clks which were enabled on error */
> + i--;
> + for (; i >= 0; i--)
> + clk_disable_unprepare(fsl_edma->muxclk[i]);
> +
> return PTR_ERR(fsl_edma->muxbase[i]);
just realized that I made a stupid mistake and overlooked that i is used again...
sorry for the noise I'll go over this again.
thx!
andi
> + }
>
> sprintf(clkname, "dmamux%d", i);
> fsl_edma->muxclk[i] = devm_clk_get(&pdev->dev, clkname);
> if (IS_ERR(fsl_edma->muxclk[i])) {
> + /* disable only clks which were enabled on error */
> + i--;
> + for (; i >= 0; i--)
> + clk_disable_unprepare(fsl_edma->muxclk[i]);
> +
> dev_err(&pdev->dev, "Missing DMAMUX block clock.\n");
> return PTR_ERR(fsl_edma->muxclk[i]);
> }
> --
> 2.11.0
>
prev parent reply other threads:[~2017-12-06 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 11:13 Andreas Platschek
2017-12-06 13:20 ` Andreas Platschek [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=20171206132045.GA5040@opentech.at \
--to=andreas.platschek@opentech.at \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vinod.koul@intel.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
Powered by JetHome