From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Jonathan Cameron <jic23@cam.ac.uk>, linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/8] staging:iio:adis16200: Do not return a error in remove function
Date: Sat, 22 Sep 2012 10:21:50 +0100 [thread overview]
Message-ID: <505D832E.5000607@kernel.org> (raw)
In-Reply-To: <1348304198-5793-1-git-send-email-lars@metafoo.de>
On 09/22/2012 09:56 AM, Lars-Peter Clausen wrote:
> 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>
Added all 8 to togreg branch of iio.git.
Eariler in the cycle I'd have pushed these as fixes, but as they've been
there a long time, lets just leave it to the next cycle.
Good catch on these btw.
> ---
> drivers/staging/iio/gyro/adis16260_core.c | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/staging/iio/gyro/adis16260_core.c b/drivers/staging/iio/gyro/adis16260_core.c
> index 1d58d0e..9571c03 100644
> --- a/drivers/staging/iio/gyro/adis16260_core.c
> +++ b/drivers/staging/iio/gyro/adis16260_core.c
> @@ -702,22 +702,16 @@ error_ret:
>
> static int __devexit adis16260_remove(struct spi_device *spi)
> {
> - int ret;
> struct iio_dev *indio_dev = spi_get_drvdata(spi);
>
> iio_device_unregister(indio_dev);
> -
> - ret = adis16260_stop_device(indio_dev);
> - if (ret)
> - goto err_ret;
> -
> + adis16260_stop_device(indio_dev);
> adis16260_remove_trigger(indio_dev);
> iio_buffer_unregister(indio_dev);
> adis16260_unconfigure_ring(indio_dev);
> iio_device_free(indio_dev);
>
> -err_ret:
> - return ret;
> + return 0;
> }
>
> /*
>
prev parent reply other threads:[~2012-09-22 9:21 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 ` [PATCH 3/8] staging:iio:ade7753: " Lars-Peter Clausen
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 ` Jonathan Cameron [this message]
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=505D832E.5000607@kernel.org \
--to=jic23@kernel.org \
--cc=jic23@cam.ac.uk \
--cc=lars@metafoo.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.