From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: [PATCH 3/8] staging:iio:ade7753: Do not return a error in remove function
Date: Sat, 22 Sep 2012 10:56:33 +0200 [thread overview]
Message-ID: <1348304198-5793-3-git-send-email-lars@metafoo.de> (raw)
In-Reply-To: <1348304198-5793-1-git-send-email-lars@metafoo.de>
In the Linux device driver model the remove callback is not allowed to fail and
the device will be removed regardless of the return value of the remove
callback. So if we abort in the remove function and do not free all resources we
will create a resource leak. Also all kinds of undefined behaviour are expected
to happen since the IIO device is still there while its parent is already gone.
The error which the driver tries to handle in the remove function is
non-critical, so we can just ignore it and continue to free all resources and
remove the IIO device.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
---
drivers/staging/iio/meter/ade7753.c | 11 +++--------
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/drivers/staging/iio/meter/ade7753.c b/drivers/staging/iio/meter/ade7753.c
index 380c05e..8b9eceb 100644
--- a/drivers/staging/iio/meter/ade7753.c
+++ b/drivers/staging/iio/meter/ade7753.c
@@ -557,18 +557,13 @@ error_ret:
/* fixme, confirm ordering in this function */
static int __devexit ade7753_remove(struct spi_device *spi)
{
- int ret;
struct iio_dev *indio_dev = spi_get_drvdata(spi);
iio_device_unregister(indio_dev);
-
- ret = ade7753_stop_device(&(indio_dev->dev));
- if (ret)
- goto err_ret;
-
+ ade7753_stop_device(&indio_dev->dev);
iio_device_free(indio_dev);
-err_ret:
- return ret;
+
+ return 0;
}
static struct spi_driver ade7753_driver = {
--
1.7.10.4
next prev parent reply other threads:[~2012-09-22 8:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 8:56 [PATCH 1/8] staging:iio:adis16200: Do not return a error in remove function Lars-Peter Clausen
2012-09-22 8:56 ` [PATCH 2/8] staging:iio:adis16400: " Lars-Peter Clausen
2012-09-22 8:56 ` Lars-Peter Clausen [this message]
2012-09-22 8:56 ` [PATCH 4/8] staging:iio:ade7754: " Lars-Peter Clausen
2012-09-22 8:56 ` [PATCH 5/8] staging:iio:ade7758: " Lars-Peter Clausen
2012-09-22 8:56 ` [PATCH 6/8] staging:iio:ade7759: " Lars-Peter Clausen
2012-09-22 8:56 ` [PATCH 7/8] staging:iio:lis3l02dq: " Lars-Peter Clausen
2012-09-22 8:56 ` [PATCH 8/8] staging:iio:sca3000: " Lars-Peter Clausen
2012-09-22 9:21 ` [PATCH 1/8] staging:iio:adis16200: " Jonathan Cameron
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=1348304198-5793-3-git-send-email-lars@metafoo.de \
--to=lars@metafoo.de \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).