From: Jonathan Cameron <jic23@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-iio@vger.kernel.org, Jonathan Cameron <jic23@cam.ac.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: (max1363) Fix probe error path
Date: Thu, 27 Dec 2012 11:14:38 +0000 [thread overview]
Message-ID: <50DC2D9E.3030006@kernel.org> (raw)
In-Reply-To: <1356330298-11443-1-git-send-email-linux@roeck-us.net>
On 12/24/2012 06:24 AM, Guenter Roeck wrote:
> Instantiating the driver with no available regulator results in:
>
> [39711.686393] i2c i2c-7: new_device: Instantiated device max1139 at 0x35
> [39711.688687] BUG: unable to handle kernel paging request at fffffffffffffe13
> [39711.688734] IP: [<ffffffff813e835b>] regulator_disable+0x1b/0x80
> [39711.688788] PGD 1c0e067 PUD 1c0f067 PMD 0
> [39711.688835] Oops: 0000 [#1] SMP
>
> Caused by bad probe error path. Fix it.
Oops.
>
> Driver should also not attempt to free the interrupt in its error path if
> none was allocated. Fix that problem as well.
>
> Finally, testing if the regulator was allocated is not necessary in the
> remove function, since the probe function bails out if this is the case.
> Remove that check.
>
Thanks Guenter. Added to the fixes-togreg branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
Might be the new year before I send Greg the pull request.
Jonathan
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
> drivers/iio/adc/max1363.c | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/iio/adc/max1363.c b/drivers/iio/adc/max1363.c
> index 1e84b5b..31f3485 100644
> --- a/drivers/iio/adc/max1363.c
> +++ b/drivers/iio/adc/max1363.c
> @@ -1605,19 +1605,20 @@ static int __devinit max1363_probe(struct i2c_client *client,
>
> return 0;
> error_free_irq:
> - free_irq(st->client->irq, indio_dev);
> + if (client->irq)
> + free_irq(st->client->irq, indio_dev);
> error_uninit_buffer:
> iio_buffer_unregister(indio_dev);
> error_cleanup_buffer:
> max1363_buffer_cleanup(indio_dev);
> error_free_available_scan_masks:
> kfree(indio_dev->available_scan_masks);
> -error_unregister_map:
> - iio_map_array_unregister(indio_dev, client->dev.platform_data);
> error_disable_reg:
> regulator_disable(st->reg);
> error_put_reg:
> regulator_put(st->reg);
> +error_unregister_map:
> + iio_map_array_unregister(indio_dev, client->dev.platform_data);
> error_free_device:
> iio_device_free(indio_dev);
> error_out:
> @@ -1635,10 +1636,8 @@ static int __devexit max1363_remove(struct i2c_client *client)
> iio_buffer_unregister(indio_dev);
> max1363_buffer_cleanup(indio_dev);
> kfree(indio_dev->available_scan_masks);
> - if (!IS_ERR(st->reg)) {
> - regulator_disable(st->reg);
> - regulator_put(st->reg);
> - }
> + regulator_disable(st->reg);
> + regulator_put(st->reg);
> iio_map_array_unregister(indio_dev, client->dev.platform_data);
> iio_device_free(indio_dev);
>
>
prev parent reply other threads:[~2012-12-27 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 6:24 [PATCH] iio: (max1363) Fix probe error path Guenter Roeck
2012-12-27 11:14 ` 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=50DC2D9E.3030006@kernel.org \
--to=jic23@kernel.org \
--cc=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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.