From: Lukas Wunner <lukas@wunner.de>
To: Mark Brown <broonie@kernel.org>, "Sanjay R Mehta" <sanju.mehta@amd.com>
Cc: linux-spi@vger.kernel.org
Subject: [PATCH 4/5] spi: amd: Fix refcount underflow on remove
Date: Mon, 4 May 2020 13:12:04 +0200 [thread overview]
Message-ID: <5e53ccdf1eecd4e015dba99d0d77389107f8a2e3.1588590210.git.lukas@wunner.de> (raw)
In-Reply-To: <cover.1588590210.git.lukas@wunner.de>
The AMD SPI driver calls spi_master_put() in its ->remove() hook even
though the preceding call to spi_unregister_master() already drops a
ref, thus leading to a refcount underflow. Drop the superfluous call
to spi_master_put().
This only leaves the call to spi_unregister_master() in the ->remove()
hook, so it's safe to change the ->probe() hook to use the devm version
of spi_register_master() and drop the ->remove() hook altogether.
Signed-off-by: Lukas Wunner <lukas@wunner.de>
---
drivers/spi/spi-amd.c | 13 +------------
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/drivers/spi/spi-amd.c b/drivers/spi/spi-amd.c
index d3e3516ef957..00f2f3405e08 100644
--- a/drivers/spi/spi-amd.c
+++ b/drivers/spi/spi-amd.c
@@ -282,7 +282,7 @@ static int amd_spi_probe(struct platform_device *pdev)
master->transfer_one_message = amd_spi_master_transfer;
/* Register the controller with SPI framework */
- err = spi_register_master(master);
+ err = devm_spi_register_master(dev, master);
if (err) {
dev_err(dev, "error %d registering SPI controller\n", err);
goto err_free_master;
@@ -296,16 +296,6 @@ static int amd_spi_probe(struct platform_device *pdev)
return err;
}
-static int amd_spi_remove(struct platform_device *pdev)
-{
- struct amd_spi *amd_spi = platform_get_drvdata(pdev);
-
- spi_unregister_master(amd_spi->master);
- spi_master_put(amd_spi->master);
-
- return 0;
-}
-
static const struct acpi_device_id spi_acpi_match[] = {
{ "AMDI0061", 0 },
{},
@@ -318,7 +308,6 @@ static struct platform_driver amd_spi_driver = {
.acpi_match_table = ACPI_PTR(spi_acpi_match),
},
.probe = amd_spi_probe,
- .remove = amd_spi_remove,
};
module_platform_driver(amd_spi_driver);
--
2.26.2
next prev parent reply other threads:[~2020-05-04 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 11:12 [PATCH 0/5] Grab bag with AMD SPI fixes Lukas Wunner
2020-05-04 11:12 ` [PATCH 1/5] spi: amd: Fix duplicate iounmap in error path Lukas Wunner
2020-05-04 11:12 ` [PATCH 2/5] spi: amd: Pass probe errors back to driver core Lukas Wunner
2020-05-04 11:12 ` [PATCH 3/5] spi: amd: Drop duplicate driver data assignments Lukas Wunner
2020-05-04 11:12 ` Lukas Wunner [this message]
2020-05-04 11:12 ` [PATCH 5/5] spi: amd: Drop superfluous member from struct amd_spi Lukas Wunner
2020-05-05 12:17 ` [PATCH 0/5] Grab bag with AMD SPI fixes 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=5e53ccdf1eecd4e015dba99d0d77389107f8a2e3.1588590210.git.lukas@wunner.de \
--to=lukas@wunner.de \
--cc=broonie@kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=sanju.mehta@amd.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).