From: Lukas Wunner <lukas@wunner.de>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, Tomer Maimon <tmaimon77@gmail.com>
Subject: [PATCH for-5.10] spi: npcm-fiu: Don't leak SPI master in probe error path
Date: Mon, 16 Nov 2020 09:23:10 +0100 [thread overview]
Message-ID: <a420c23a363a3bc9aa684c6e790c32a8af106d17.1605512876.git.lukas@wunner.de> (raw)
In-Reply-To: <73adc6ba84a4f968f2e1499a776e5c928fbdde56.1605512876.git.lukas@wunner.de>
If the calls to of_match_device(), of_alias_get_id(),
devm_ioremap_resource(), devm_regmap_init_mmio() or devm_clk_get()
fail on probe of the NPCM FIU SPI driver, the spi_controller struct is
erroneously not freed.
Fix by switching over to the new devm_spi_alloc_master() helper.
Fixes: ace55c411b11 ("spi: npcm-fiu: add NPCM FIU controller driver")
Signed-off-by: Lukas Wunner <lukas@wunner.de>
Cc: <stable@vger.kernel.org> # v5.4+: 5e844cc37a5c: spi: Introduce device-managed SPI controller allocation
Cc: <stable@vger.kernel.org> # v5.4+
Cc: Tomer Maimon <tmaimon77@gmail.com>
---
drivers/spi/spi-npcm-fiu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/spi/spi-npcm-fiu.c b/drivers/spi/spi-npcm-fiu.c
index 341f7cffeaac..1cb9329de945 100644
--- a/drivers/spi/spi-npcm-fiu.c
+++ b/drivers/spi/spi-npcm-fiu.c
@@ -679,7 +679,7 @@ static int npcm_fiu_probe(struct platform_device *pdev)
struct resource *res;
int id;
- ctrl = spi_alloc_master(dev, sizeof(*fiu));
+ ctrl = devm_spi_alloc_master(dev, sizeof(*fiu));
if (!ctrl)
return -ENOMEM;
--
2.28.0
next prev parent reply other threads:[~2020-11-16 11:43 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 8:23 [PATCH for-5.10] spi: spi-geni-qcom: Fix use-after-free on unbind Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] spi: spi-qcom-qspi: " Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] spi: spi-sh: " Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] spi: pxa2xx: " Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] spi: rpc-if: " Lukas Wunner
2020-11-28 20:20 ` Sergey Shtylyov
2020-11-29 11:35 ` Lukas Wunner
2020-11-30 19:18 ` Sergey Shtylyov
2020-12-02 11:43 ` Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] spi: mxic: Don't leak SPI master in probe error path Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] spi: mt7621: " Lukas Wunner
2020-11-16 11:05 ` Stefan Roese
2020-11-16 8:23 ` [PATCH for-5.10] spi: spi-mtk-nor: " Lukas Wunner
2020-11-17 4:02 ` Ikjoon Jang
2020-11-17 12:32 ` Mark Brown
2020-11-16 8:23 ` [PATCH for-5.10] spi: gpio: " Lukas Wunner
2020-11-16 19:23 ` Andrey Smirnov
2020-11-16 23:03 ` Lukas Wunner
2020-11-16 23:59 ` Andrey Smirnov
2020-11-18 1:08 ` Linus Walleij
2020-11-16 8:23 ` Lukas Wunner [this message]
2020-11-17 22:38 ` [PATCH for-5.10] spi: npcm-fiu: " Mark Brown
2020-12-01 13:57 ` Mark Brown
2020-12-01 14:30 ` Lukas Wunner
2020-12-01 17:17 ` Mark Brown
2020-12-01 17:49 ` Lukas Wunner
2020-12-02 15:17 ` Mark Brown
2020-11-16 8:23 ` [PATCH for-5.10] spi: rb4xx: " Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] spi: sc18is602: " Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] media: netup_unidvb: " Lukas Wunner
2020-11-23 14:06 ` Mauro Carvalho Chehab
2020-12-01 13:57 ` Mark Brown
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=a420c23a363a3bc9aa684c6e790c32a8af106d17.1605512876.git.lukas@wunner.de \
--to=lukas@wunner.de \
--cc=broonie@kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=tmaimon77@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;
as well as URLs for NNTP newsgroup(s).