From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Richard Weinberger <richard@nod.at>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-mtd@lists.infradead.org, Kamal Dasu <kdasu.kdev@gmail.com>
Subject: Re: [PATCH v2 08/16] mtd: rawnand: fsmc: fix and enhance probe function error path
Date: Tue, 27 Mar 2018 10:05:23 +0200 [thread overview]
Message-ID: <20180327100523.07ab908f@bbrezillon> (raw)
In-Reply-To: <20180321130157.9524-9-miquel.raynal@bootlin.com>
On Wed, 21 Mar 2018 14:01:49 +0100
Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> An error after nand_scan_tail() should trigger a nand_cleanup().
>
> Also, goto labels should indicate what the next cleanup is, not the
> point from which they can be accessed.
Can you split that in 2 patches: one changing the error labels, and
another one adding the missing nand_cleanup()?
>
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> ---
> drivers/mtd/nand/raw/fsmc_nand.c | 27 +++++++++++++++------------
> 1 file changed, 15 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/mtd/nand/raw/fsmc_nand.c b/drivers/mtd/nand/raw/fsmc_nand.c
> index 28c48dcc514e..f4a5a317d4ae 100644
> --- a/drivers/mtd/nand/raw/fsmc_nand.c
> +++ b/drivers/mtd/nand/raw/fsmc_nand.c
> @@ -1022,12 +1022,12 @@ static int __init fsmc_nand_probe(struct platform_device *pdev)
> host->read_dma_chan = dma_request_channel(mask, filter, NULL);
> if (!host->read_dma_chan) {
> dev_err(&pdev->dev, "Unable to get read dma channel\n");
> - goto err_req_read_chnl;
> + goto disable_clk;
> }
> host->write_dma_chan = dma_request_channel(mask, filter, NULL);
> if (!host->write_dma_chan) {
> dev_err(&pdev->dev, "Unable to get write dma channel\n");
> - goto err_req_write_chnl;
> + goto release_dma_read_chan;
> }
> }
>
> @@ -1050,7 +1050,7 @@ static int __init fsmc_nand_probe(struct platform_device *pdev)
> ret = nand_scan_ident(mtd, 1, NULL);
> if (ret) {
> dev_err(&pdev->dev, "No NAND Device found!\n");
> - goto err_scan_ident;
> + goto release_dma_write_chan;
> }
>
> if (AMBA_REV_BITS(host->pid) >= 8) {
> @@ -1065,7 +1065,7 @@ static int __init fsmc_nand_probe(struct platform_device *pdev)
> dev_warn(&pdev->dev, "No oob scheme defined for oobsize %d\n",
> mtd->oobsize);
> ret = -EINVAL;
> - goto err_probe;
> + goto release_dma_write_chan;
> }
>
> mtd_set_ooblayout(mtd, &fsmc_ecc4_ooblayout_ops);
> @@ -1090,7 +1090,7 @@ static int __init fsmc_nand_probe(struct platform_device *pdev)
>
> default:
> dev_err(&pdev->dev, "Unsupported ECC mode!\n");
> - goto err_probe;
> + goto release_dma_write_chan;
> }
>
> /*
> @@ -1110,7 +1110,7 @@ static int __init fsmc_nand_probe(struct platform_device *pdev)
> "No oob scheme defined for oobsize %d\n",
> mtd->oobsize);
> ret = -EINVAL;
> - goto err_probe;
> + goto release_dma_write_chan;
> }
> }
> }
> @@ -1118,26 +1118,29 @@ static int __init fsmc_nand_probe(struct platform_device *pdev)
> /* Second stage of scan to fill MTD data-structures */
> ret = nand_scan_tail(mtd);
> if (ret)
> - goto err_probe;
> + goto release_dma_write_chan;
>
> mtd->name = "nand";
> ret = mtd_device_register(mtd, NULL, 0);
> if (ret)
> - goto err_probe;
> + goto cleanup_nand;
>
> platform_set_drvdata(pdev, host);
> dev_info(&pdev->dev, "FSMC NAND driver registration successful\n");
> +
> return 0;
>
> -err_probe:
> -err_scan_ident:
> +cleanup_nand:
> + nand_cleanup(nand);
> +release_dma_write_chan:
> if (host->mode == USE_DMA_ACCESS)
> dma_release_channel(host->write_dma_chan);
> -err_req_write_chnl:
> +release_dma_read_chan:
> if (host->mode == USE_DMA_ACCESS)
> dma_release_channel(host->read_dma_chan);
> -err_req_read_chnl:
> +disable_clk:
> clk_disable_unprepare(host->clk);
> +
> return ret;
> }
>
--
Boris Brezillon, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-03-27 8:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 13:01 [PATCH v2 00/16] Fix probe functions error path Miquel Raynal
2018-03-21 13:01 ` [PATCH v2 01/16] mtd: rawnand: brcmnand: fix probe function " Miquel Raynal
2018-03-21 13:01 ` [PATCH v2 02/16] mtd: rawnand: cafe: " Miquel Raynal
2018-03-27 8:02 ` Boris Brezillon
2018-03-21 13:01 ` [PATCH v2 03/16] mtd: rawnand: davinci: " Miquel Raynal
2018-03-21 13:01 ` [PATCH v2 04/16] mtd: rawnand: denali: " Miquel Raynal
2018-03-21 13:01 ` [PATCH v2 05/16] mtd: rawnand: docg4: fix the " Miquel Raynal
2018-03-27 7:59 ` Boris Brezillon
2018-03-21 13:01 ` [PATCH v2 06/16] mtd: rawnand: fsl_elbc: fix " Miquel Raynal
2018-03-27 7:56 ` Boris Brezillon
2018-03-21 13:01 ` [PATCH v2 07/16] mtd: rawnand: fsl_ifc: " Miquel Raynal
2018-03-27 7:57 ` Boris Brezillon
2018-03-21 13:01 ` [PATCH v2 08/16] mtd: rawnand: fsmc: fix and enhance " Miquel Raynal
2018-03-27 8:05 ` Boris Brezillon [this message]
2018-03-21 13:01 ` [PATCH v2 09/16] mtd: rawnand: mxc: fix " Miquel Raynal
2018-03-21 13:01 ` [PATCH v2 10/16] mtd: rawnand: omap2: fix the " Miquel Raynal
2018-03-21 13:01 ` [PATCH v2 11/16] mtd: rawnand: sh_flctl: " Miquel Raynal
2018-03-21 13:01 ` [PATCH v2 12/16] mtd: rawnand: tango: fix " Miquel Raynal
2018-03-21 13:01 ` [PATCH v2 13/16] mtd: rawnand: hisi504: fix and enhance the " Miquel Raynal
2018-03-27 8:56 ` Boris Brezillon
2018-03-21 13:01 ` [PATCH v2 14/16] mtd: rawnand: lpc32xx_mlc: " Miquel Raynal
2018-03-21 13:01 ` [PATCH v2 15/16] mtd: rawnand: lpc32xx_slc: " Miquel Raynal
2018-03-21 13:01 ` [PATCH v2 16/16] mtd: rawnand: s3c2410: " Miquel Raynal
2018-03-27 9:06 ` Boris Brezillon
2018-04-21 17:56 ` Miquel Raynal
2018-03-28 8:38 ` [PATCH v2 00/16] Fix probe functions " Boris Brezillon
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=20180327100523.07ab908f@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=kdasu.kdev@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=yamada.masahiro@socionext.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