From: boris.brezillon@bootlin.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd: nxp-spifi: decrement flash_np refcnt on error paths
Date: Wed, 9 May 2018 11:42:50 +0200 [thread overview]
Message-ID: <20180509114250.120eb299@bbrezillon> (raw)
In-Reply-To: <1525812456-25877-1-git-send-email-khoroshilov@ispras.ru>
On Tue, 8 May 2018 23:47:36 +0300
Alexey Khoroshilov <khoroshilov@ispras.ru> wrote:
> nxp_spifi_probe() increments refcnt of SPI flash device node by
> of_get_next_available_child() and then it passes the node
> to mtd device in nxp_spifi_setup_flash().
> But if a failure happens before mtd_device_register() succeed,
> the refcnt is left undecremented.
Why not doing that in the error path of the probe function? Also, you
probably want to call of_node_put() in the ->remove() function.
>
> Found by Linux Driver Verification project (linuxtesting.org).
>
> Signed-off-by: Alexey Khoroshilov <khoroshilov@ispras.ru>
> ---
> drivers/mtd/spi-nor/nxp-spifi.c | 16 +++++++++++-----
> 1 file changed, 11 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/mtd/spi-nor/nxp-spifi.c b/drivers/mtd/spi-nor/nxp-spifi.c
> index 15374216d4d9..8919e31f2ab8 100644
> --- a/drivers/mtd/spi-nor/nxp-spifi.c
> +++ b/drivers/mtd/spi-nor/nxp-spifi.c
> @@ -294,7 +294,8 @@ static int nxp_spifi_setup_flash(struct nxp_spifi *spifi,
> break;
> default:
> dev_err(spifi->dev, "unsupported rx-bus-width\n");
> - return -EINVAL;
> + ret = -EINVAL;
> + goto err_node_put;
> }
> }
>
> @@ -328,7 +329,8 @@ static int nxp_spifi_setup_flash(struct nxp_spifi *spifi,
> break;
> default:
> dev_err(spifi->dev, "only mode 0 and 3 supported\n");
> - return -EINVAL;
> + ret = -EINVAL;
> + goto err_node_put;
> }
>
> writel(ctrl, spifi->io_base + SPIFI_CTRL);
> @@ -356,22 +358,26 @@ static int nxp_spifi_setup_flash(struct nxp_spifi *spifi,
> ret = spi_nor_scan(&spifi->nor, NULL, &hwcaps);
> if (ret) {
> dev_err(spifi->dev, "device scan failed\n");
> - return ret;
> + goto err_node_put;
> }
>
> ret = nxp_spifi_setup_memory_cmd(spifi);
> if (ret) {
> dev_err(spifi->dev, "memory command setup failed\n");
> - return ret;
> + goto err_node_put;
> }
>
> ret = mtd_device_register(&spifi->nor.mtd, NULL, 0);
> if (ret) {
> dev_err(spifi->dev, "mtd device parse failed\n");
> - return ret;
> + goto err_node_put;
> }
>
> return 0;
> +
> +err_node_put:
> + of_node_put(np);
> + return ret;
> }
>
> static int nxp_spifi_probe(struct platform_device *pdev)
next prev parent reply other threads:[~2018-05-09 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 20:47 [PATCH] mtd: nxp-spifi: decrement flash_np refcnt on error paths Alexey Khoroshilov
2018-05-09 9:42 ` Boris Brezillon [this message]
2018-05-09 14:35 ` Alexey Khoroshilov
2018-05-09 14:39 ` Boris Brezillon
2018-05-09 14:56 ` [PATCH v2] mtd: nxp-spifi: release flash_np in nxp_spifi_probe() Alexey Khoroshilov
2018-05-09 15:03 ` Boris Brezillon
2018-05-09 15:11 ` [PATCH v3] " Alexey Khoroshilov
2018-07-07 6:58 ` 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=20180509114250.120eb299@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.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